5 Moose::Manual::Types - Moose's type system
9 Moose provides its own type system for attributes. You can also use
10 these types to validate method parameters with the help of a MooseX
13 Moose's type system is based on a combination of Perl 5's own
14 I<implicit> types and some Perl 6 concepts. You can easily create your
15 own subtypes with custom constraints, making it easy to express any
18 Types have names, and you can re-use them by name, making it easy to
19 share types throughout a large application.
21 Let us be clear that is not a "real" type system. Moose does not
22 magically make Perl start associating types with variables. This is
23 just an advanced parameter checking system which allows you to
24 associate a name with a constraint.
26 That said, it's still pretty damn useful, and we think it's one of the
27 things that makes Moose both fun and powerful. Taking advantage of the
28 type system makes it much easier to ensure that you are getting valid
29 data, and it also contributes greatly to code maintainability.
33 The basic Moose type hierarchy looks like this
57 In practice, the only difference between C<Any> and C<Item> is
58 conceptual. C<Item> is used as the top-level type in the hierarchy.
60 The rest of these types correspond to existing Perl concepts. For
61 example, a C<Num> is anything that Perl thinks looks like a number. An
62 C<Object> is a blessed reference, etc.
64 The types followed by "[`a]" can be parameterized. So instead of just
65 plain C<ArrayRef> we can say that we want C<ArrayRef[Int]> instead. We
66 can even do something like C<HashRef[ArrayRef[Str]]>.
68 The C<Maybe[`a]> type deserves a special mention. Used by itself, it
69 doesn't really mean anything (and is equivalent to C<Item>). When it
70 is parameterized, it means that the value is either C<undef> or the
71 parameterized type. So C<Maybe[Int]> means an integer or C<undef>
73 For more details on the type hierarchy, see
74 L<Moose::Util::TypeConstraints>.
76 =head1 WHAT IS A TYPE?
78 It's important to realize that types are not classes (or
79 packages). Types are just objects (L<Moose::Meta::TypeConstraint>
80 objects, to be exact) with a name and a constraint. Moose maintains a
81 global type registry that lets it convert names like C<Num> into the
84 However, class names I<can be> type names. When you define a new class
85 using Moose, it defines an associated type name behind the scenes:
91 Now you can use C<'MyApp::User'> as a type name:
98 However, for non-Moose classes there's no magic. You may have to
99 explicitly declare the class type. This is a bit muddled because Moose
100 assumes that any unknown type name passed as the C<isa> value for an
101 attribute is a class. So this works:
103 has 'birth_date' => (
108 In general, when Moose is presented with an unknown name, it assumes
109 that the name is a class:
111 subtype 'ModernDateTime'
113 => where { $_->year() >= 1980 }
114 => message { 'The date you provided is not modern enough' };
116 has 'valid_dates' => (
118 isa => 'ArrayRef[DateTime]',
121 Moose will assume that C<DateTime> is a class name in both of these
126 Moose uses subtypes in its built-in hierarchy. C<Int> is a child of
129 A subtype is defined in terms of a parent type and a constraint. Any
130 constraints defined by the parent(s) will be checked first, and then
131 the the subtype's. A value must pass I<all> of these checks to be
132 valid for the subtype.
134 Typically, a subtype takes the parent's constraint and makes it more
137 A subtype can also define its own constraint failure message. This
138 lets you do things like have an error "The value you provided (20),
139 was not a valid rating, which must be a number from 1-10." This is
140 much friendlier than the default error, which just says that the value
141 failed a validation check for the type.
143 Here's a simple (and useful) subtype example:
145 subtype 'PositiveInt'
148 => message { "The number you provided, $_, was not a positive number" }
150 Note that the sugar functions for working with types are all exported
151 by L<Moose::Util::TypeConstraints>.
153 =head2 Creating a new type (that isn't a subtype)
155 You can also create new top-level types:
157 type 'FourCharacters' => where { defined $_ && length $_ == 4 };
159 In practice, this example is more or less the same as subtyping
160 C<Str>, except you have to check definedness yourself.
162 It's hard to find a case where you wouldn't want to subtype a very
163 broad type like C<Defined>, C<Ref> or C<Object>.
165 Defining a new top-level type is conceptually the same as subtyping
170 Type names are global throughout the current Perl
171 interpreter. Internally, Moose maps names to type objects via a
172 L<registry|Moose::Meta::TypeConstraint::Registry>.
174 If you have multiple apps or libraries all using Moose in the same
175 process, you could have problems with collisions. We recommend that
176 you prefix names with some sort of namespace indicator to prevent
177 these sorts of collisions.
179 For example, instead of calling a type "PositiveInt", call it
180 "MyApp.Type.PositiveInt".
182 Type names are just strings. We recommend that you I<do not> use "::"
183 as a separator in type names. This can be very confusing, because
184 class names are I<also> valid type names! Using something else, like a
185 period, makes it clear that "MyApp::User" is a class and
186 "MyApp.Type.PositiveInt" is a Moose type defined by your application.
188 The L<MooseX::Types> module lets you create bareword aliases to longer
189 names and also automatically namespaces all the types you define.
193 One of the most powerful features of Moose's type system is its
194 coercions. A coercion is a way to convert from one type to another.
196 subtype 'ArrayRefOfInts'
197 => as 'ArrayRef[Int]';
199 coerce 'ArrayRefOfInts'
203 You'll note that we had to create a subtype rather than coercing
204 C<ArrayRef[Int]> directly. This is just a quirk of how Moose
207 Coercions, like type names, are global. This is I<another> reason why
208 it is good to namespace your types. Moose will I<never> try to coerce
209 a value unless you explicitly ask for it. This is done by setting the
210 C<coerce> attribute parameter to a true value:
216 isa => 'ArrayRefOfInts',
220 Foo->new( sizes => 42 );
222 This code example will do the right thing, and the newly created
223 object will have C<[ 42 ]> as its C<sizes> attribute.
227 Deep coercion is the coercion of type parameters for parameterized
228 types. Let's take these types as an example:
232 => where { /[a-f0-9]/i };
240 isa => 'ArrayRef[Int]',
244 If we try passing an array reference of hex numbers for the C<sizes>
245 attribute, Moose will not do any coercion.
247 However, you can define a set of subtypes to enable coercion between
248 two parameterized types.
250 subtype 'ArrayRefOfHexNums'
251 => as 'ArrayRef[HexNum]';
253 subtype 'ArrayRefOfInts'
254 => as 'ArrayRef[Int]';
256 coerce 'ArrayRefOfInts'
257 => from 'ArrayRefOfHexNums'
258 => via { [ map { hex } @{$_} ] };
260 Foo->new( sizes => [ 'a1', 'ff', '22' ] );
262 Now Moose will coerce the hex numbers to integers.
264 However, Moose does not attempt to chain coercions, so it will not
265 coerce a single hex number. To do that, we need to define a separate
268 coerce 'ArrayRefOfInts'
270 => via { [ hex $_ ] };
272 Yes, this can all get verbose, but coercion is tricky magic, and we
273 think it's best to make it explicit.
277 Moose allows you to say that an attribute can be of two or more
278 disparate types. For example, we might allow an C<Object> or
283 isa => 'Object | FileHandle',
286 Moose actually parses that string and recognizes that you are creating
287 a type union. The C<output> attribute will accept any sort of object,
288 as well as an unblessed file handle. It is up to you to do the right
289 thing for each of them in your code.
291 Whenever you use a type union, you should consider whether or not
292 coercion might be a better answer.
294 For our example above, we might want to be more specific, and insist
295 that output be an object with a C<print> method:
299 => where { $_->can('print') };
301 We can coerce file handles to an object that satisfies this condition
302 with a simple wrapper class:
315 my $fh = $self->handle();
320 Now we can define a coercion from C<FileHandle> to our wrapper class:
324 => via { FHWrapper->new( handle => $_ ) };
332 This pattern of using a coercion instead of a type union will help
333 make your class internals simpler.
335 =head1 TYPE CREATION HELPERS
337 The L<Moose::Util::TypeConstraints> module exports a number of helper
338 functions for creating specific kinds of types. These include
339 C<class_type>, C<role_type>, and C<maybe_type>. See the docs for
342 One helper worth noting is C<enum>, which allows you to create a
343 subtype of C<Str> that only allows the specified values:
345 enum 'RGB' => qw( red green blue );
347 This creates a type named C<RGB>
349 =head1 ANONYMOUS TYPES
351 All of the type creation functions return a type object. This type
352 object can be used wherever you would use a type name, as a parent
353 type, or as the value for an attribute's C<isa> parameter:
357 isa => subtype 'Int' => where { $_ > 0 },
360 This is handy when you want to create a one-off type and don't want to
361 "pollute" the global namespace registry.
363 =head1 VALIDATING METHOD PARAMETERS
365 Moose does not provide any means of validating method
366 parameters. However, there are several MooseX extensions on CPAN which
369 The simplest and least sugary is L<MooseX::Params::Validate>. This
370 lets you validate a set of named parameters using Moose types:
373 use MooseX::Params::Validate;
377 my %params = validated_hash(
379 bar => { isa => 'Str', default => 'Moose' },
384 L<MooseX::Params::Validate> also supports coercions.
386 There are several more powerful extensions that support method
387 parameter validation using Moose types, including
388 L<MooseX::Method::Signatures>, which gives you a full-blown C<method>
391 method morning (Str $name) {
392 $self->say("Good morning ${name}!");
395 =head1 LOAD ORDER ISSUES
397 Because Moose types are defined at runtime, you may run into load
398 order problems. In particular, you may want to use a class's type
399 constraint before that type has been defined.
401 We have several recommendations for ameliorating this problem. First,
402 define I<all> of your custom types in one module,
403 C<MyApp::Types>. Second, load this module in all of your other
406 If you are still having load order problems, you can make use of the
407 C<find_type_constraint> function exported by
408 L<Moose::Util::TypeConstraints>:
410 class_type('MyApp::User')
411 unless find_type_constraint('MyApp::User') || ;
413 This sort of "find or create" logic is simple to write, and will let
414 you work around load order issues.
418 Dave Rolsky E<lt>autarch@urth.orgE<gt>
420 =head1 COPYRIGHT AND LICENSE
422 Copyright 2009 by Infinity Interactive, Inc.
424 L<http://www.iinteractive.com>
426 This library is free software; you can redistribute it and/or modify
427 it under the same terms as Perl itself.