*Top posted*

Generally, you're suggesting a good feature. Having build-time checks of correct values/keys is important, but we still want to have users be able to provide their own keys and values. This is what helps make Dancer MVC-ish, because you can separate the view and model information in your configuration using any number of plugins or even in-house code for it.

A possible solution would be to:
1. add a special key in the hash for user-defined information
2. allow the use to set their own keys/values in inner levels, thus never breaking non-existing plugins/engines.

I would like to get more input on this from our architect, Sukria.

On Wed, Dec 15, 2010 at 9:37 AM, Gabor Szabo <szabgab@gmail.com> wrote:

On Wed, Dec 15, 2010 at 3:39 AM, Naveed Massjouni <naveedm9@gmail.com> wrote:
> On Tue, Dec 14, 2010 at 6:03 PM, Gabor Szabo <szabgab@gmail.com> wrote:
>>

>> BTW I also tried to add a configuration parameter that does not exists
>> and it was silently disregarded. As it could be the result of a typo or
>> a misunderstanding I think that should be reported as well.
>
> I don't agree with this. I put my own app specific params in the config. Like
> max_widgets: 100

I have not reached the point yet to understand how I can add project
specific params
there but I would hope there is (or will be) some clear separation
between the parameters
that belong to various parts of the application. Name space for the
config parameters?

Otherwise how is it ensured that a future paramtername of Dancer or
one of the plugins
does not have the same name as the one in your application?

In addition I hope there can be a way to let Dancer check the validity of
your parameters as well e.g. by providing a declaration of accepted
parameters, accepted values and default values to each parameter.

Gabor

http://szabgab.com/
_______________________________________________
Dancer-users mailing list
Dancer-users@perldancer.org
http://www.backup-manager.org/cgi-bin/listinfo/dancer-users