[Dancer-users] Invalid value for log config

Flavio Poletti polettix at gmail.com
Tue Feb 22 15:08:30 CET 2011


On Tue, Feb 22, 2011 at 1:52 PM, David Precious <davidp at preshweb.co.uk>wrote:

>
> > Anything that is defined in the top-level would be considered Dancer's
> > core property.
> >
> > This would allow for specific checks, and could protect users from using
> > a key that would become Dancer-native in future versions.
> >
> > I like that idea, but my main concern here is backward-compat, as I
> said...
>
>
> Personally, I like the simplicity of being able to shove your app's own
> config at the top level of the config file, and just say e.g.
> config->{foo} in your code.
>

I would propose to add a new configuration (a-la "strict") in order to
decide whether top-level configurations are allowed or not. Then, it could
be possible to set strict as default... or not, and let the user decide.

Cheers,

    Flavio.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.backup-manager.org/pipermail/dancer-users/attachments/20110222/e017968e/attachment.htm>


More information about the Dancer-users mailing list