[Catalyst-dev] RFC - ConfigLoader interface improvement

John Napiorkowski jjn1056 at yahoo.com
Sun Aug 27 02:41:11 CEST 2006


Personally I think it's a good idea.  I would prefer a base config file of stuff I use on all servers for a given project and then another for server specific stuff.  I know some of the config modules already have this built in but I think it would be a good best practices for catalyst.

--john

----- Original Message ----
From: Joel Bernstein <joel at fysh.org>
To: catalyst-dev at lists.rawmode.org
Sent: Tuesday, August 22, 2006 10:47:21 PM
Subject: [Catalyst-dev] RFC - ConfigLoader interface improvement

Hi,

After reading Fayland Lam's mail to the list, asking why:
    __PACKAGE__->config( files => [ qw( filea fileb filec ) ] );
doesn't work, I checked the synopsis of ConfigLoader and noted that
there is nothing to suggest it /ought/ to work.

However, it shouldn't be difficult to implement that behaviour, if
people want it. I'm already working on a new version of ConfigLoader, so
I could add that feature to it with relative ease. I don't see any
problem with adding it to the existing LTjake ConfigLoader code too, and
making an interim release to CPAN to satisfy Fayland. 

What do you guys think about this? Is there any reason why people should
/not/ be able to supply multiple config files? I guess anything he can
do with several he could also do with one file, but I can see the logic
in breaking up class-specific config into separate files. 

Comments? Bad idea? Shall I go ahead and make up a patch?

/joel

_______________________________________________
Catalyst-dev mailing list
Catalyst-dev at lists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst-dev






More information about the Catalyst-dev mailing list