- New upstream release 0.30
- Added a new option for named params, "return_object", which causes the
validation sub to return an object with methods for each param rather than
a hashref; this is a great way to avoid typos in hash keys (idea
shamelessly stolen from Toby Inkster's Type::Params module)
- Tweaked the POD formatting so that the table of contents generated by
MetaCPAN is more useful
- Optionally use Class::XSAccessor
- New upsteram release 0.27
- Fixed a bug with inlining Moose types: if a type's parent needed
environment variables, those would not get closed over (GH#22)
- Added a debug option to dump the source of the subroutine before it is
eval'd
- New upstream release 0.25
- All exceptions now include a stack trace by default when treated as a
string; this makes finding where validation failed a lot easier (GH#18)
- The name for a subroutine is now used in some exception messages, even if
Sub::Util cannot be installed
- 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
- 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
- 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)
- 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
- 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
- New upstream release 0.17
- When using positional parameters, parameters with a default are now
optional; for named parameters, this was already the case
- 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
- 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
Paul Howarth
Fedora Release Engineering