Commit Graph

14 Commits

Author SHA1 Message Date
Jitka Plesnikova 0da309bf02 Perl 5.26 rebuild 2017-06-06 00:37:23 +02:00
Paul Howarth 134722a0a6 Update to 0.24
- New upstream release 0.24
  - The source_for() exported by Params::ValidationCompiler did not work at all
    (GH#16)
2017-04-11 19:38:40 +01:00
Fedora Release Engineering de50ce375a - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild 2017-02-11 04:47:15 +00:00
Paul Howarth b642bdbfc6 Update to 0.23
- New upstream release 0.23
  - Trying to create a validator for positional parameters where a required
    param came after one with a default did not throw an exception
  - A positional params validator with a slurpy type that had coercions did not
    return the coerced values; it returned the original values instead
2017-01-23 20:28:02 +00:00
Paul Howarth 71efe4d965 Update to 0.22
- New upstream release 0.22
  - Explicitly load the B module; previously, the code relied on this already
    being loaded by something else (GH#11)
  - Removed the alpha warning from the docs
2016-12-31 16:52:18 +00:00
Paul Howarth b94649ffec Update to 0.21
- New upstream release 0.21
  - Switched to using GitHub issues
2016-12-07 11:40:31 +00:00
Paul Howarth 48cfdf25a8 Update to 0.20
- New upstream release 0.20
  - The keys for parameter specifications are now validated, and if an unknown
    key is seen then an exception will be thrown; this will help you catch
    typos in your parameter specification (GH#8)
2016-12-06 10:31:56 +00:00
Paul Howarth 756179fa7a Update to 0.19
- New upstream release 0.19
  - Non-inlinable Specio types caused a syntax error when used with positional
    params
  - Positional params with coercions and defaults did not work properly; the
    coerced value and the default would simply not be returned in any case
2016-11-22 09:25:01 +00:00
Paul Howarth 5b75ebeaef Update to 0.18
- New upstream release 0.18
  - Using coercions with positional parameters could cause a "Modification of a
    read-only value attempted" exception when the generated code tried to
    assign to elements of @_; this is now fixed by making a copy if any of the
    types have a coercion
  - Using Moose types with coercions in a positional params check would cause
    invalid code to be generated; this could also happen with Type::Tiny if
    either the type or a coercion could not be inlined
2016-11-14 10:25:56 +00:00
Paul Howarth 38c6162026 Update to 0.17
- New upstream release 0.17
  - When using positional parameters, parameters with a default are now
    optional; for named parameters, this was already the case
2016-11-07 09:13:58 +00:00
Paul Howarth 80bd12eb8a Update to 0.16
- New upstream release 0.16
  - Previously, using a default with a positional parameter would result in an
    error when compiling the validator subroutine; defaults now work with
    positional parameters (GH#5)
  - Moose and Specio types (and coercions) that provide variables to close over
    when being inlined did not always compile properly; most notably, this was
    not being handled at all for Moose types, and not completely handled for
    Specio coercions
2016-11-04 12:07:56 +00:00
Paul Howarth 0a9febde93 Update to 0.14
- New upstream release 0.14
  - Added a "named_to_list" option to support returning only the parameter
    values from a named parameter validator rather than the key-value pairs
  - Errors from calls to validation_for() now use croak so as to show up at the
    call site, rather than in the internals
2016-11-03 11:55:05 +00:00
Petr Písař 6313c66174 Break build cycle: perl-Moose → perl-DateTime → perl-Params-ValidationCompiler 2016-10-26 13:21:06 +02:00
Paul Howarth f9b3c33dea Initial import (perl-Params-ValidationCompiler-0.13-3)
Create a customized, optimized, non-lobotomized, uncompromised, and thoroughly
specialized parameter checking subroutine.
2016-09-19 15:33:13 +01:00