-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] make flag not found
a reason
#2950
Comments
Thanks for the suggestion @piclemx ! My main concern here is that this can lead to confusion if you e.g. miss-spell or miss-reference a flag by mistake. This is at-least the main motivation for flag not found being a fail-fast error. I think this is pretty common in the FF space and e.g. how OpenFeature also handles these evaluation semantics (FLAG_NOT_FOUND is an error code not a reason): |
flag not found
a reason
Problem
When looking at the output of an evaluation of a boolean flag that doesn't exist, I think it would be preferable that the Flipt API returns that the Flag is false. IMO boolean flag should always consider false by default if nothing is provided.
Ideal Solution
Would like more something like
Search
Additional Context
No response
The text was updated successfully, but these errors were encountered: