Data::FormValidator::Constraints - Basic sets of constraints on input profile.
In an Data::FormValidator profile:
constraints => { email => "email", fax => "american_phone", phone => "american_phone", state => "state", },
Those are the builtin constraints that can be specified by name in the input profiles.
Checks if the email LOOKS LIKE an email address. This checks if the input contains one @, and a two level domain name. The address portion is checked quite liberally. For example, all those probably invalid address would pass the test :
nobody@top.domain %?&/$()@nowhere.net guessme@guess.m
This one checks if the input correspond to an american state or a canadian province.
This one checks if the input is a valid two letter abbreviation of an american state.
This checks if the input is a two letter canadian province abbreviation.
This constraints checks if the input is an american zipcode or a canadian postal code.
This constraints checks if the input is a valid Canadian postal code.
This input validator checks if the input is a valid american zipcode : 5 digits followed by an optional mailbox number.
This one checks if the input looks like a phone number, (if it contains at least 6 digits.)
This constraints checks if the number is a possible North American style of phone number : (XXX) XXX-XXXX. It has to contains 7 or more digits.
This is takes two parameters, the credit card number and the credit cart type. You should take the hash reference option for using that constraint.
The number is checked only for plausibility, it checks if the number could be valid for a type of card by checking the checksum and looking at the number of digits and the number of digits of the number.
This functions is only good at weeding typos and such. IT DOESN'T CHECK IF THERE IS AN ACCOUNT ASSOCIATED WITH THE NUMBER.
This one checks if the input is in the format MM/YY or MM/YYYY and if the MM part is a valid month (1-12) and if that date is not in the past.
This one checks if the input field starts by M(asterCard), V(isa), A(merican express) or D(iscovery).
This checks if the input is formatted like an IP address (v4)
Data::FormValidator also includes built-in support for using any of regular expressions in Regexp::Common as named constraints. Simply use the name of regular expression you want. This works whether you want to untaint the data or not. For example:
constraints => { my_ip_address => 'RE_net_IPv4', }
Some Regexp::Common regular expressions support additional flags that are expected to be passed into the routine as arguments. We support this as well. Just use hash style method of declaring a constraint, and the params key:
params
constraints => { my_ip_address => { constraint => 'RE_net_IPv4', params => [ \'-sep'=> \' ' ], } }
Yes, it's a bit strange that you have pass the values to param by reference using the backslash ("\"). This is necessary to preserve some important backward compatibility that I haven't figured out how to work around yet.
Be sure to check out the Regexp::Common syntax for how its syntax works. It will make more sense to add future regular expressions to Regexp::Common rather than to Data::FormValidator.
You may also call these functions directly through the procedural interface by either importing them directly or importing the whole :validators group. This is useful if you want to use the built-in validators out of the usual profile specification interface.
For example, if you want to access the email validator directly, you could either do:
use Data::FormValidator::Constraints (qw/valid_email/); or use Data::FormValidator::Constraints (:validators); if (valid_email($email)) { # do something with the email address }
Notice that when you call validators directly, you'll need to prefix the validator name with "valid_"
Each validator also has a version that returns the untainted value if the validation succeeded. You may call these functions directly through the procedural interface by either importing them directly or importing the :matchers group. For example if you want to untaint a value with the email validator directly you may:
if ($email = match_email($email)) { system("echo $email"); } else { die "Unable to validate email"; }
Notice that when you call validators directly and want them to return an untainted value, you'll need to prefix the validator name with "match_"
Data::FormValidator(3), Data::FormValidator::Filters(3), Data::FormValidator::ConstraintsFactory(3), Regexp::Common
Some of those input validation functions have been taken from MiniVend by Michael J. Heins <mike@heins.net>
The credit card checksum validation was taken from contribution by Bruce Albrecht <bruce.albrecht@seag.fingerhut.com> to the MiniVend program.
Francis J. Lacoste <francis.lacoste@iNsu.COM> Michael J. Heins <mike@heins.net> Bruce Albrecht <bruce.albrecht@seag.fingerhut.com>
Copyright (c) 1999 iNsu Innovations Inc. All rights reserved.
Parts Copyright 1996-1999 by Michael J. Heins <mike@heins.net> Parts Copyright 1996-1999 by Bruce Albrecht <bruce.albrecht@seag.fingerhut.com>
This program is free software; you can redistribute it and/or modify it under the terms as perl itself.
1 POD Error
The following errors were encountered while parsing the POD:
You forgot a '=back' before '=head1'
To install Data::FormValidator, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Data::FormValidator
CPAN shell
perl -MCPAN -e shell install Data::FormValidator
For more information on module installation, please visit the detailed CPAN module installation guide.