An extension of params::validate using moose's types
version 0.18
package Foo;
use Moose;
use MooseX::Params::Validate;
sub foo {
my ( $self, %params ) = validated_hash(
\@_,
bar => { isa => 'Str', default => 'Moose' },
);
return "Hooray for $params{bar}!";
}
sub bar {
my $self = shift;
my ( $foo, $baz, $gorch ) = validated_list(
\@_,
foo => { isa => 'Foo' },
baz => { isa => 'ArrayRef | HashRef', optional => 1 },
gorch => { isa => 'ArrayRef[Int]', optional => 1 }
);
[ $foo, $baz, $gorch ];
}
This module fills a gap in Moose by adding method parameter validation to Moose. This is just one of many developing options, it should not be considered the \*(L"official\*(R" one by any means though.
You might also want to explore \*(C`MooseX::Method::Signatures\*(C' and \*(C`MooseX::Declare\*(C'.
It is not possible to introspect the method parameter specs; they are created as needed when the method is called and cached for subsequent calls.
This behaves similarly to the standard Params::Validate \*(C`validate\*(C' function and returns the captured values in a \s-1HASH\s0. The one exception is where if it spots an instance in the @_, then it will handle it appropriately (unlike Params::Validate which forces you to shift you $self first). The values in @_ can either be a set of name-value pairs or a single hash reference. The %parameter_spec accepts the following options:
The \*(C`isa\*(C' option can be either; class name, Moose type constraint name or an anon Moose type constraint.
The \*(C`does\*(C' option can be either; role name or an anon Moose type constraint.
This is the default value to be used if the value is not supplied.
As with Params::Validate, all options are considered required unless otherwise specified. This option is passed directly to Params::Validate.
If this is true and the parameter has a type constraint which has coercions, then the coercion will be called for this parameter. If the type does have coercions, then this parameter is ignored.
This function is also available under its old name, \*(C`validate\*(C'.
The %parameter_spec accepts the same options as above, but returns the parameters as positional values instead of a \s-1HASH\s0. This is best explained by example: sub foo { my ( $self, $foo, $bar ) = validated_list( \@_, foo => { isa => 'Foo' }, bar => { isa => 'Bar' }, ); $foo->baz($bar); } We capture the order in which you defined the parameters and then return them as a list in the same order. If a param is marked optional and not included, then it will be set to \*(C`undef\*(C'. The values in @_ can either be a set of name-value pairs or a single hash reference. Like \*(C`validated_hash\*(C', if it spots an object instance as the first parameter of @_, it will handle it appropriately, returning it as the first argument. This function is also available under its old name, \*(C`validatep\*(C'. This function validates a list of positional parameters. Each $spec should validate one of the parameters in the list: sub foo { my $self = shift; my ( $foo, $bar ) = pos_validated_list( \@_, { isa => 'Foo' }, { isa => 'Bar' }, );
... } Unlike the other functions, this function cannot find $self in the argument list. Make sure to shift it off yourself before doing validation. The values in @_ must be a list of values. You cannot pass the values as an array reference, because this cannot be distinguished from passing one value which is itself an array reference. If a parameter is marked as optional and is not present, it will simply not be returned. If you want to pass in any of the cache control parameters described below, simply pass them after the list of parameter validation specs: sub foo { my $self = shift; my ( $foo, $bar ) = pos_validated_list( \@_, { isa => 'Foo' }, { isa => 'Bar' }, MX_PARAMS_VALIDATE_NO_CACHE => 1, );
... }
By default, any parameters not mentioned in the parameter spec cause this module to throw an error. However, you can have have this module simply ignore them by setting \*(C`MX_PARAMS_VALIDATE_ALLOW_EXTRA\*(C' to a true value when calling a validation subroutine.
When calling \*(C`validated_hash\*(C' or \*(C`pos_validated_list\*(C' the extra parameters are simply returned in the hash or list as appropriate. However, when you call \*(C`validated_list\*(C' the extra parameters will not be returned at all. You can get them by looking at the original value of @_.
By default, this module exports the \*(C`validated_hash\*(C', \*(C`validated_list\*(C', and \*(C`pos_validated_list\*(C'.
If you would prefer to import the now deprecated functions \*(C`validate\*(C' and \*(C`validatep\*(C' instead, you can use the \*(C`:deprecated\*(C' tag to import them.
When a validation subroutine is called the first time, the parameter spec is prepared and cached to avoid unnecessary regeneration. It uses the fully qualified name of the subroutine (package + subname) as the cache key. In 99.999% of the use cases for this module, that will be the right thing to do.
However, I have (ab)used this module occasionally to handle dynamic sets of parameters. In this special use case you can do a couple things to better control the caching behavior.
Passing in the \*(C`MX_PARAMS_VALIDATE_NO_CACHE\*(C' flag in the parameter spec this will prevent the parameter spec from being cached. sub foo { my ( $self, %params ) = validated_hash( \@_, foo => { isa => 'Foo' }, MX_PARAMS_VALIDATE_NO_CACHE => 1, );
}
Passing in \*(C`MX_PARAMS_VALIDATE_CACHE_KEY\*(C' with a value to be used as the cache key will bypass the normal cache key generation. sub foo { my ( $self, %params ) = validated_hash( \@_, foo => { isa => 'Foo' }, MX_PARAMS_VALIDATE_CACHE_KEY => 'foo-42', );
}
Dave Rolsky <[email protected]>
Please submit bugs to the \s-1CPAN\s0 \s-1RT\s0 system at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=moosex-params-validate or via email at [email protected].
Stevan Little <[email protected]>
Dave Rolsky <[email protected]>
This software is copyright (c) 2013 by Stevan Little <[email protected]>.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.