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