Skip to content
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

Add support for optional values #130

Closed
yakovmanshin opened this issue Apr 30, 2024 · 0 comments · Fixed by #143
Closed

Add support for optional values #130

yakovmanshin opened this issue Apr 30, 2024 · 0 comments · Fixed by #143
Labels
breaking This issue breaks compatibility with previous versions new New feature or request research The topic needs research and clarification
Milestone

Comments

@yakovmanshin
Copy link
Owner

No description provided.

@yakovmanshin yakovmanshin added new New feature or request breaking This issue breaks compatibility with previous versions labels Apr 30, 2024
@yakovmanshin yakovmanshin added this to the v4.0.0 milestone Apr 30, 2024
@yakovmanshin yakovmanshin added the research The topic needs research and clarification label May 11, 2024
yakovmanshin added a commit that referenced this issue 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
Labels
breaking This issue breaks compatibility with previous versions new New feature or request research The topic needs research and clarification
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant