mminella/grails-feature-toggle — comment on commit 4640130b3bc7fdbac9018746c55cb2596b498ad2
File: grails-app/conf/Config.groovy line 35
By ryannorris:

Let's call it a nice to have. I think this is really a configuration item, and I prefer to keep configuration externalizable. Precedence would be that the annotation parameter contains the default, and configuration can always override it. Here's my use case: I want to return a 404 in production, but want to redirect in development.

Sent from my iPhone

On Jan 31, 2012, at 6:10 PM, Michael Minella wrote:

> Exposing the configuration at this level makes sense but then you get into the issue of precedence. Do you assume that the annotation overrides the config (since it would be more finely grained)? Same thing goes for the annotation in general. I have it currently coded to take the more finely grained levels first (closure, method the class) so you can override the higher levels at a lower level if needed.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/mminella/grails-feature-toggle/commit/4640130b3bc7fdbac9018746c55cb2596b498ad2#commitcomment-920573