1 package MooseX::StrictConstructor;
8 use Moose::Util::MetaRole;
9 use MooseX::StrictConstructor::Role::Object;
14 if ( $Moose::VERSION < 1.9900 ) {
15 require MooseX::StrictConstructor::Trait::Method::Constructor;
18 'MooseX::StrictConstructor::Trait::Method::Constructor']
22 require MooseX::StrictConstructor::Trait::Class;
24 = ( class => ['MooseX::StrictConstructor::Trait::Class'] );
27 Moose::Exporter->setup_import_methods(
28 class_metaroles => \%class_meta,
29 base_class_roles => ['MooseX::StrictConstructor::Role::Object'],
35 # ABSTRACT: Make your object constructors blow up on unknown attributes
46 use MooseX::StrictConstructor;
52 # this blows up because color is not a known attribute
53 My::Class->new( size => 5, color => 'blue' );
57 Simply loading this module makes your constructors "strict". If your
58 constructor is called with an attribute init argument that your class
59 does not declare, then it calls "Carp::confess()". This is a great way
62 =head2 Subverting Strictness
64 You may find yourself wanting to have your constructor accept a
65 parameter which does not correspond to an attribute.
67 In that case, you'll probably also be writing a C<BUILD()> or
68 C<BUILDARGS()> method to deal with that parameter. In a C<BUILDARGS()>
69 method, you can simply make sure that this parameter is not included
70 in the hash reference you return. Otherwise, in a C<BUILD()> method,
71 you can delete it from the hash reference of parameters.
77 if ( delete $params->{do_something} ) {
84 Please report any bugs or feature requests to
85 C<bug-moosex-strictconstructor@rt.cpan.org>, or through the web
86 interface at L<http://rt.cpan.org>. I will be notified, and then
87 you'll automatically be notified of progress on your bug as I make