Much clearer. Thanks.

On 28 October 2013 at 14:34:27, Robert Jackson (notifications@github.com) wrote:

In source/guides/configuring-ember/feature-flags.md:

> +
> +## Enabling At Runtime
> +
> +Remember that the only time a feature can be enabled at runtime is if the
> +`features.json` for that build contains `null` (technically, anything other
> +than `true` or `false` will do, but `null` is the chosen value). If the feature
> +is present in `features.json` with a `null` value there are a couple different
> +ways to enable it at runtime.
> +
> +Declare an `ENV.FEATURES` global before requiring Ember:
> +
> +```javascript
> +ENV = {FEATURES: {'link-to': true}};
> +```
> +
> +Set the `Ember.FEATURES` value after initialization:
Just updated to add more clarification, can you review and confirm that the recent changes clears up the ambiguity?

—
Reply to this email directly or view it on GitHub.