Revision history for Perl extension MooseX::ConfigFromFile
+0.02 - Jan 23, 2008
+ - Honor any default supplied for the configfile attribute
+
0.01 - Dec 18, 2007
- Initial release
test_requires 'Test::More' => '0.42';
-requires 'Moose' => '0';
-requires 'MooseX::Types::Path::Class' => '0';
+requires 'Moose' => '0.35';
+requires 'MooseX::Types::Path::Class' => '0.04';
# Rebuild README for maintainers
system("pod2text lib/MooseX/ConfigFromFile.pm >README") if -e 'MANIFEST.SKIP';
use Moose;
with 'MooseX::SomeSpecificConfigRole';
+ # optionally, default the configfile:
+ has +configfile ( default => '/tmp/foo.yaml' );
+
# ... insert your stuff here ...
########
"new_with_config", and requires that concrete roles derived from it
implement the class method "get_config_from_file".
+ Attributes specified directly as arguments to "new_with_config"
+ supercede those in the configfile.
+
MooseX::Getopt knows about this abstract role, and will use it if
available to load attributes from the file specified by the commandline
flag "--configfile" during its normal "new_with_options".
Attributes
configfile
This is a Path::Class::File object which can be coerced from a regular
- pathname string. This is the file your attributes are loaded from.
+ pathname string. This is the file your attributes are loaded from. You
+ can add a default configfile in the class using the role and it will be
+ honored at the appropriate time:
+
+ has +configfile ( default => '/etc/myapp.yaml' );
Class Methods
new_with_config
get_config_from_file
This class method is not implemented in this role, but it is required of
all subroles. Its two arguments are the classname and the configfile,
- and it is expected to return a hashref of arguments to pass to "new()".
+ and it is expected to return a hashref of arguments to pass to "new()"
+ which are sourced from the configfile.
meta
The Moose meta stuff, included here because otherwise pod tests fail
use Moose::Role;
use MooseX::Types::Path::Class qw( File );
-our $VERSION = '0.01';
+our $VERSION = '0.02';
requires 'get_config_from_file';
sub new_with_config {
my ($class, %opts) = @_;
- if($opts{configfile}) {
- %opts = (%{$class->get_config_from_file($opts{configfile})}, %opts);
+ my $configfile;
+
+ if(defined $opts{configfile}) {
+ $configfile = $opts{configfile}
+ }
+ else {
+ my $cfmeta = $class->meta->get_attribute('configfile');
+ $configfile = $cfmeta->default if $cfmeta->has_default;
+ }
+
+ if(defined $configfile) {
+ %opts = (%{$class->get_config_from_file($configfile)}, %opts);
}
+
$class->new(%opts);
}
use Moose;
with 'MooseX::SomeSpecificConfigRole';
+ # optionally, default the configfile:
+ has +configfile ( default => '/tmp/foo.yaml' );
+
# ... insert your stuff here ...
########
and requires that concrete roles derived from it implement the class method
C<get_config_from_file>.
+Attributes specified directly as arguments to C<new_with_config> supercede those
+in the configfile.
+
L<MooseX::Getopt> knows about this abstract role, and will use it if available
to load attributes from the file specified by the commandline flag C<--configfile>
during its normal C<new_with_options>.
=head2 configfile
This is a L<Path::Class::File> object which can be coerced from a regular pathname
-string. This is the file your attributes are loaded from.
+string. This is the file your attributes are loaded from. You can add a default
+configfile in the class using the role and it will be honored at the appropriate time:
+
+ has +configfile ( default => '/etc/myapp.yaml' );
=head1 Class Methods
This class method is not implemented in this role, but it is required of all subroles.
Its two arguments are the classname and the configfile, and it is expected to return
-a hashref of arguments to pass to C<new()>.
+a hashref of arguments to pass to C<new()> which are sourced from the configfile.
=head2 meta