1 package MooseX::StrictConstructor;
8 use Moose::Util::MetaRole;
11 my %class_meta = ( class => ['MooseX::StrictConstructor::Trait::Class'] );
13 if ( $Moose::VERSION < 1.9900 ) {
14 require MooseX::StrictConstructor::Trait::Method::Constructor;
15 $class_meta{constructor}
16 = ['MooseX::StrictConstructor::Trait::Method::Constructor'];
19 Moose::Exporter->setup_import_methods(
20 class_metaroles => \%class_meta,
26 # ABSTRACT: Make your object constructors blow up on unknown attributes
37 use MooseX::StrictConstructor;
43 # this blows up because color is not a known attribute
44 My::Class->new( size => 5, color => 'blue' );
48 Simply loading this module makes your constructors "strict". If your
49 constructor is called with an attribute init argument that your class
50 does not declare, then it calls C<Moose->throw_error()>. This is a great way
53 =head2 Subverting Strictness
55 You may find yourself wanting to have your constructor accept a
56 parameter which does not correspond to an attribute.
58 In that case, you'll probably also be writing a C<BUILD()> or
59 C<BUILDARGS()> method to deal with that parameter. In a C<BUILDARGS()>
60 method, you can simply make sure that this parameter is not included
61 in the hash reference you return. Otherwise, in a C<BUILD()> method,
62 you can delete it from the hash reference of parameters.
68 if ( delete $params->{do_something} ) {
75 Please report any bugs or feature requests to
76 C<bug-moosex-strictconstructor@rt.cpan.org>, or through the web
77 interface at L<http://rt.cpan.org>. I will be notified, and then
78 you'll automatically be notified of progress on your bug as I make