On Tue, Feb 22, 2011 at 1:52 PM, David Precious <davidp@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.