You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2024. It is now read-only.
When a feature flag cannot be found, the client logs at the WARN level:
Unknown feature flag example-feature-flag-key; returning default value
We find it useful in test mode to rely on the default value for features, and only enable/disable features as required. This means we don't have to configure our application to load a default flag list into the client.
The resulting logging statements are painful, and we would like if they could be suppressed in test mode.
The text was updated successfully, but these errors were encountered:
@drichelson Apart from changing granularity of Logger class to suppress this message, is there any other way ?
I also have a feature flag for TEST mode & want to rely on default value for it. don't want to define it in LD portal for all our envs.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a feature flag cannot be found, the client logs at the WARN level:
Unknown feature flag example-feature-flag-key; returning default value
We find it useful in test mode to rely on the default value for features, and only enable/disable features as required. This means we don't have to configure our application to load a default flag list into the client.
The resulting logging statements are painful, and we would like if they could be suppressed in test mode.
The text was updated successfully, but these errors were encountered: