[#132] Error Throwing in Feature-Flag Stores #139
Merged
Conversation
This file contains 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
yakovmanshin
added
new
yakovmanshin
added a commit
that referenced
this pull request
May 12, 2024
* Previously, feature-flag stores returned `nil` when the value was not found * This behavior made it impossible to distinguish between the absence of a value and a literal `nil` value * While this distinction wasn’t important in the majority of cases, it could be sometimes * For that reason, optional values were not supported in YMFF * #132 / #139 changed the protocols for feature-flag stores so they throw errors instead of returning `nil` for nonexistent values * This change made it possible to accept `nil` as a valid feature-flag value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[Closes #132]
FeatureFlagResolver