MooseX::Types - Organise your Moose types in libraries
version 0.50
package MyLibrary;
# predeclare our own types
use MooseX::Types -declare => [
qw(
PositiveInt
NegativeInt
ArrayRefOfPositiveInt
ArrayRefOfAtLeastThreeNegativeInts
LotsOfInnerConstraints
StrOrArrayRef
MyDateTime
)
];
# import builtin types
use MooseX::Types::Moose qw/Int HashRef/;
# type definition.
subtype PositiveInt,
as Int,
where { $_ > 0 },
message { "Int is not larger than 0" };
subtype NegativeInt,
as Int,
where { $_ < 0 },
message { "Int is not smaller than 0" };
# type coercion
coerce PositiveInt,
from Int,
via { 1 };
# with parameterized constraints.
subtype ArrayRefOfPositiveInt,
as ArrayRef[PositiveInt];
subtype ArrayRefOfAtLeastThreeNegativeInts,
as ArrayRef[NegativeInt],
where { scalar(@$_) > 2 };
subtype LotsOfInnerConstraints,
as ArrayRef[ArrayRef[HashRef[Int]]];
# with TypeConstraint Unions
subtype StrOrArrayRef,
as Str|ArrayRef;
# class types
class_type 'DateTime';
# or better
class_type MyDateTime, { class => 'DateTime' };
coerce MyDateTime,
from HashRef,
via { DateTime->new(%$_) };
1;
package Foo;
use Moose;
use MyLibrary qw( PositiveInt NegativeInt );
# use the exported constants as type names
has 'bar',
isa => PositiveInt,
is => 'rw';
has 'baz',
isa => NegativeInt,
is => 'rw';
sub quux {
my ($self, $value);
# test the value
print "positive\n" if is_PositiveInt($value);
print "negative\n" if is_NegativeInt($value);
# coerce the value, NegativeInt doesn't have a coercion
# helper, since it didn't define any coercions.
$value = to_PositiveInt($value) or die "Cannot coerce";
}
1;
The type system provided by Moose effectively makes all of its builtin type
global, as are any types you declare with Moose. This means that every module
that declares a type named PositiveInt is sharing the same type object. This
can be a problem when different parts of the code base want to use the same
name for different things.
This package lets you declare types using short names, but behind the scenes
it namespaces all your type declarations, effectively prevent name clashes
between packages.
This is done by creating a type library module like MyApp::Types and then
importing types from that module into other modules.
As a side effect, the declaration mechanism allows you to write type names as
barewords (really function calls), which catches typos in names at compile
time rather than run time.
This module also provides some helper functions for using Moose types outside
of attribute declarations.
If you mix string-based names with types created by this module, it will warn,
with a few exceptions. If you are declaring a class_type() or
role_type() within your type library, or if you use a fully qualified name
like "MyApp::Foo" .
A MooseX::Types is just a normal Perl module. Unlike Moose
itself, it does not install use strict and use warnings in your
class by default, so this is up to you.
The only thing a library is required to do is
use MooseX::Types -declare => \@types;
with @types being a list of types you wish to define in this library.
This line will install a proper base class in your package as well as the
full set of handlers for your declared
types. It will then hand control over to the Moose::Util::TypeConstraints manpage'
import method to export the functions you will need to declare your
types.
If you want to use Moose' built-in types (e.g. for subtyping) you will
want to
use MooseX::Types::Moose @types;
to import the helpers from the shipped the MooseX::Types::Moose manpage
library which can export all types that come with Moose.
You will have to define coercions for your types or your library won't
export a to_$type coercion helper for it.
Note that you currently cannot define types containing :: , since
exporting would be a problem.
You also don't need to use warnings and strict , since the
definition of a library automatically exports those.
You can import the ``type helpers'' of a
library by use ing it with a list of types to import as arguments. If
you want all of them, use the :all tag. For example:
use MyLibrary ':all';
use MyOtherLibrary qw( TypeA TypeB );
MooseX::Types comes with a library of Moose' built-in types called
the MooseX::Types::Moose manpage.
The exporting mechanism is, since version 0.5, implemented via a wrapper
around the Sub::Exporter manpage. This means you can do something like this:
use MyLibrary TypeA => { -as => 'MyTypeA' },
TypeB => { -as => 'MyTypeB' };
A constant with the name of your type. It contains the type's fully
qualified name. Takes no value, as all constants.
This handler takes a value and tests if it is a valid value for this
$type . It will return true or false.
A handler that will take a value and coerce it into the $type . It will
return a false value if the type could not be coerced.
Important Note: This handler will only be exported for types that can
do type coercion. This has the advantage that a coercion to a type that
has not defined any coercions will lead to a compile-time error.
You can define your own wrapper subclasses to manipulate the behaviour
of a set of library exports. Here is an example:
package MyWrapper;
use strict;
use MRO::Compat;
use base 'MooseX::Types::Wrapper';
sub coercion_export_generator {
my $class = shift;
my $code = $class->next::method(@_);
return sub {
my $value = $code->(@_);
warn "Coercion returned undef!"
unless defined $value;
return $value;
};
}
1;
This class wraps the coercion generator (e.g., to_Int() ) and warns
if a coercion returned an undefined value. You can wrap any library
with this:
package Foo;
use strict;
use MyWrapper MyLibrary => [qw( Foo Bar )],
Moose => [qw( Str Int )];
...
1;
The Moose library name is a special shortcut for the MooseX::Types::Moose manpage.
- type_export_generator( $short, $full )
-
Creates a closure returning the type's the Moose::Meta::TypeConstraint manpage object.
- check_export_generator( $short, $full, $undef_message )
-
This creates the closure used to test if a value is valid for this type.
- coercion_export_generator( $short, $full, $undef_message )
-
This is the closure that's doing coercions.
- $short
-
The short, exported name of the type.
- $full
-
The fully qualified name of this type as Moose knows it.
- $undef_message
-
A message that will be thrown when type functionality is used but the
type does not yet exist.
As of version 0.08, the Moose::Types manpage has experimental support for Recursive
subtypes. This will allow:
subtype Tree() => as HashRef[Str|Tree];
Which validates things like:
{key=>'value'};
{key=>{subkey1=>'value', subkey2=>'value'}}
And so on. This feature is new and there may be lurking bugs so don't be afraid
to hunt me down with patches and test cases if you have trouble.
the MooseX::Types manpage uses the MooseX::Types::TypeDecorator manpage to do some overloading
which generally allows you to easily create union types:
subtype StrOrArrayRef,
as Str|ArrayRef;
As with parameterized constraints, this overloading extends to modules using the
types you define in a type library.
use Moose;
use MooseX::Types::Moose qw(HashRef Int);
has 'attr' => ( isa => HashRef | Int );
And everything should just work as you'd think.
Installs the the MooseX::Types::Base manpage class into the caller and exports types
according to the specification described in LIBRARY DEFINITION. This
will continue to the Moose::Util::TypeConstraints manpage' import method to export
helper functions you will need to declare your types.
Generate a type export, e.g. Int() . This will return either a
the Moose::Meta::TypeConstraint manpage object, or alternatively a
the MooseX::Types::UndefinedType manpage object if the type was not yet defined.
Given a String $name with @args find the matching type constraint and parameterize
it with @args.
Given a String $name, find the matching type constraint.
Given a $type_constraint, return a lightweight the MooseX::Types::TypeDecorator manpage
instance.
This generates a coercion handler function, e.g. to_Int($value) .
Generates a constraint check closure, e.g. is_Int($value) .
The following are lists of gotchas and their workarounds for developers coming
from the standard string based type constraint names
A library makes the types quasi-unique by prefixing their names with (by
default) the library package name. If you're only using the type handler
functions provided by MooseX::Types, you shouldn't ever have to use
a type's actual full name.
The perlop manpage has this to say about the '=>' operator: ``The => operator is
a synonym for the comma, but forces any word (consisting entirely of word
characters) to its left to be interpreted as a string (as of 5.001). This
includes words that might otherwise be considered a constant or function call.''
Due to this stringification, the following will NOT work as you might think:
subtype StrOrArrayRef => as Str | ArrayRef;
The StrOrArrayRef type will have its stringification activated -- this causes the
subtype to not be created. Since the bareword type constraints are not strings
you really should not try to treat them that way. You will have to use the ','
operator instead. The authors of this package realize that all the Moose
documentation and examples nearly uniformly use the '=>' version of the comma
operator and this could be an issue if you are converting code.
Patches welcome for discussion.
If you want to use the Sub::Exporter manpage with a Type Library, you need to make sure
you export all the type constraints declared AS WELL AS any additional export
targets. For example if you do:
package TypeAndSubExporter;
use MooseX::Types::Moose qw(Str);
use MooseX::Types -declare => [qw(MyStr)];
use Sub::Exporter -setup => { exports => [qw(something)] };
subtype MyStr, as Str;
sub something {
return 1;
}
# then in another module ...
package Foo;
use TypeAndSubExporter qw(MyStr);
You'll get a "MyStr" is not exported by the TypeAndSubExporter module error.
It can be worked around by:
- use Sub::Exporter -setup => { exports => [ qw(something) ] };
+ use Sub::Exporter -setup => { exports => [ qw(something MyStr) ] };
This is a workaround and I am exploring how to make these modules work better
together. I realize this workaround will lead a lot of duplication in your
export declarations and will be onerous for large type libraries. Patches and
detailed test cases welcome. See the tests directory for a start on this.
You may want to combine a set of types for your application with other type
libraries, like the MooseX::Types::Moose manpage or the MooseX::Types::Common::String manpage.
The the MooseX::Types::Combine manpage module provides a simple API for combining a set
of type libraries together.
Moose, the Moose::Util::TypeConstraints manpage, the MooseX::Types::Moose manpage,
the Sub::Exporter manpage
Many thanks to the #moose cabal on irc.perl.org .
Bugs may be submitted through the RT bug tracker
(or bug-MooseX-Types@rt.cpan.org).
There is also a mailing list available for users of this distribution, at
http://lists.perl.org/list/moose.html.
There is also an irc channel available for users of this distribution, at
#moose on irc.perl.org .
Robert ``phaylon'' Sedlacek <rs@474.at>
This software is copyright (c) 2007 by Robert ``phaylon'' Sedlacek.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
|