On Tue, Oct 11, 2011 at 04:30:25PM +0200, Peter Gordon wrote:
> I am trying to find a decent design pattern for Moose validation of
> user input. All the Moose examples I have found either assume that
> the data is correct or else dies.
...
> From an OOP perspective, it seems to me that the valid
On Oct 11, 2011, at 10:30 AM, Peter Gordon wrote:
> I am trying to find a decent design pattern for Moose validation of
> user input. All the Moose examples I have found either assume that
> the data is correct or else dies.
>
> Example:
> package Address ;
> use Moose;
> use Moose::Util::TypeCo
Peter Gordon wrote:
I am trying to find a decent design pattern for Moose validation of
user input. All the Moose examples I have found either assume that
the data is correct or else dies.
You might be interested in using:
https://metacpan.org/module/Data::Verifier
Which lets you filter, ve
I am trying to find a decent design pattern for Moose validation of
user input. All the Moose examples I have found either assume that
the data is correct or else dies.
Example:
package Address ;
use Moose;
use Moose::Util::TypeConstraints;
subtype 'Email',
as 'Str',
where { $_ =~ m!
