++ed by:

5 PAUSE users
1 non-PAUSE user.

Cory G Watson


Data::Verifier - Profile based data verification with Moose type constraints.


Data::Verifier allows you verify data (such as web forms, which was the original idea) by leveraging the power of Moose's type constraint system.

    use Data::Verifier;

    my $dv = Data::Verifier->new(
        filters => [ qw(trim) ]
        profile => {
            name => {
                required    => 1,
                type        => 'Str',
                filters     => [ qw(collapse) ]
            age  => {
                type        => 'Int';
            sign => {
                required    => 1,
                type        => 'Str'

    my $results = $dv->verify({
        name => 'Cory', age => 'foobar'

    $results->success; # no

    $results->is_invalid('name'); # no
    $results->is_invalid('age');  # yes

    $results->is_missing('name'); # no
    $results->is_missing('sign'); # yes

    $results->get_original_value('name'); # Unchanged, original value
    $results->get_value('name'); # Filtered, valid value
    $results->get_value('age');  # undefined, as it's invalid


Data::Verifier firstly intends to leverage Moose's type constraint system, which is significantly more powerful than anything I could create for the purposes of this module. Secondly it aims to keep a fairly simple interface by leveraging the aforementioned type system to keep options to a minumum.



Define a coercion to use for verification. This will not define a global Moose type coercion, but is instead just a single coercion to apply to a specific entity.

    my $verifier = Data::Verifier->new(
        profile => {
            a_string => {
                type     => 'Str',
                coercion => Data::Verifier::coercion(
                    from => 'Int', 
                        via => sub { (qw[ one two three ])[ ($_ - 1) ] }

Now, after a_string is processed by Data::Verifier, the results will return the coerced and validated value.



An optional arrayref of filter names through which all values will be passed.


The profile is a hashref. Each value you'd like to verify is a key. The values specify all the options to use with the field. The available options are:


If true then the value will be given an opportunity to coerce via Moose's type system. If this is set, coercion will be ignored.


Set this attribute to the coercion defined for this type. If coerce is set this attribute will be ignored. See the coercion method above.


Allows a set of fields to be specifid as dependents of this one. The argument for this key is a full-fledged profile as you would give to the profile key:

  my $verifier = Data::Verifier->new(
      profile => {
          password    => {
              dependent => {
                  password2 => {
                      required => 1,

In the above example password is not required. If it is provided then password2 must also be provided. If any depedents of a field are missing or invalid then that field is invalid. In our example if password is provided and password2 is missing then password will be invalid.


An optional list of filters through which this specific value will be run. See the documentation for Data::Verifier::Filters to learn more. This value may be either a string or an arrayref of strings.


An optional length which the value may not exceed.


An optional length which the value may not be less.


The post_check key takes a subref and, after all verification has finished, executes the subref with the results of the verification as it's only argument. The subref's return value determines if the field to which the post_check belongs is invalid. A typical example would be when the value of one field must be equal to the other, like an email confirmation:

  my $verifier = Data::Verifier->new(
      profile => {
          email    => {
              required => 1,
              dependent => {
                  email2 => {
                      required => 1,
              post_check => sub {
                  my $r = shift;
                  return $r->get_value('email') eq $r->get_value('email2');

  my $results = $verifier->verify({
      email => 'foo@example.com', email2 => 'foo2@example.com'

  $results->success; # false
  $results->is_valid('email'); # false
  $results->is_valid('email2); # true, as it has no post_check

In the above example, success will return false, because the value of email does not match the value of email2. is_valid will return false for email but true for email2, since nothing specifically invalidated it. In this example you should rely on the email field, as email2 carries no significance but to confirm email.

Note about post_check and exceptions: If have a more complex post_check that could fail in multiple ways, you can die in your post_check coderef and the exception will be stored in the fields reason attribute.


Determines if this field is required for verification.


The name of the Moose type constraint to use with verifying this field's value.


It may be important to understand the order in which the various steps of verification are performed:

Global Filters

Any global filters in the profile are executed.

Per-Field Filters

Any per-field filters are executed.

Empty String Check

If the value of the field is an empty string then it is changed to an undef.

Required Check

The parameter must now be defined if it is set as required.

Length Check

Minimum then maximum length is checked.

Type Check (w/Coercion)

At this point the type will be checked after an optional coercion.

Depedency Checks

If this field has dependents then those will not be processed.

Post Check

If the field has a post check it will now be executed.


Cory G Watson, <gphat at cpan.org>


J. Shirley

Stevan Little


Copyright 2009 Cold Hard Code, LLC

This program is free software; you can redistribute it and/or modify it under the terms of either: the GNU General Public License as published by the Free Software Foundation; or the Artistic License.

See http://dev.perl.org/licenses/ for more information.