Upstream changes:
4.80 Nov 1st, 2012
[NEW FEATURES]
- New built-in constraint_methods to test the number of values submitted for a
particular field:
FV_num_values(1),
FV_num_values_between(1,2), # inclusive
One way that garbage can get through a Data::FormValidator profile is
when two values are submitted when only one is intended. In this
case, this application could end up with a values like this:
ARRAY(0x841214c)
Using these new constraints, you can precisely control how many values
are allowed for each field.
[INTERNAL]
- Source control hosting has been moved to http://hub.darcs.net
You can now browse, pull and fork the darcs repo through this website.
4.71 Oct 2nd, 2012
[BUG FIXES]
- Custom messages for built-in constraints work again. It appears that this
was broken in 4.70, which triggered a sleeper bug.
(Thanks to Lee Carmichael, Mark Stosberg, RT##73235)
4.70 11/11/11
[NEW FEATURES]
- Built-in constraints in Constraints.pm can now be renamed:
constraint_methods => {
first_names => {
constraint_method => FV_max_length(3),
name => 'custom_length',
}
},
(Thanks to heinst@arqs.com.br for the suggestion, RT#49477)
[INTERNALS]
- modernize Constraints.pm and Results.pm a bit.
- Module::Build added to configure_requires in Build.PL
4.67 11/11/11
[INTERNALS]
- modernize FormValidator.pm internals a bit
- Update META.yml to exclude an internal package from getting indexed.
5ced506c3c