Repository navigation
feat(flags): accept a caller default in FeatureFlagEvaluations#enabled? #285
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| 'posthog-ruby': minor | ||
| --- | ||
|
|
||
| Add an optional `default_value:` keyword to `PostHog::FeatureFlagEvaluations#enabled?`. It is returned when the flag has no value in the snapshot β it was never loaded, the `/flags` request failed, or no flag with that key exists β while a flag that does have a value, including `false` and variant strings, still wins over the default. A flag the server returned but marked as failed resolves to `false`, not the default. Calls that omit the keyword keep returning `false` for a missing flag. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
/flagsmarks a flagfailed: true(witherrorsWhileComputingFlags),evaluate_flagsstill stores it asenabled: false. That meansflagisn't nil here, so the default never applies. I confirmed this with a failing spec:{ 'f' => { enabled: false, failed: true } }makesenabled?('f', default_value: true)returnfalse. The doc comment and changeset both say the default covers "the evaluation failed", and that's the main fail-open case callers want this for. I think we need to treat failed records as having no value (skip them inevaluate_flags, or carryfailedon the record and check it here). Otherwise we should drop that clause from the docs and changeset.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed the docs rather than the behavior in 25100ed. posthog-node's
evaluateFlagsstores failed flags the same way, andisEnabledonly falls back todefaultValuewhen the key is absent, so skipping them here would put Ruby out of step with node.The doc comment and changeset now say the default covers a failed
/flagsrequest (nothing in the snapshot at all), and that a flag the server marked failed resolves tofalse. Added specs for both, including your repro.If we want fail-open on per-flag failures, I think that's a cross-SDK change and better raised in sdk-specs first.