-
Notifications
You must be signed in to change notification settings - Fork 24.9k
RN: Fix Typing for Non-Boolean Feature Flags #51707
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
Conversation
This pull request was exported from Phabricator. Differential Revision: D75690997 |
Summary: Currently, the type definitions for feature flags assumes `boolean` values in the `expectedReleaseValue` field. This diff fixes them so `expectedReleaseValue` must match the type of `defaultValue`. Changelog: [Internal] Differential Revision: D75690997
a04d625
to
020f598
Compare
This pull request was exported from Phabricator. Differential Revision: D75690997 |
Summary: Currently, the type definitions for feature flags assumes `boolean` values in the `expectedReleaseValue` field. This diff fixes them so `expectedReleaseValue` must match the type of `defaultValue`. Changelog: [Internal] Differential Revision: D75690997
Summary: Currently, the feature flag system does not properly support non-boolean feature flags. The type definitions and generated code make assumptions about the value type being `boolean`. This diff fixes these assumptions so that non-boolean feature flags are supported. Changelog: [Internal] Differential Revision: D75690997
020f598
to
4481aa1
Compare
This pull request was exported from Phabricator. Differential Revision: D75690997 |
Summary: Currently, the feature flag system does not properly support non-boolean feature flags. The type definitions and generated code make assumptions about the value type being `boolean`. This diff fixes these assumptions so that non-boolean feature flags are supported. Changelog: [Internal] Differential Revision: D75690997
Summary: Pull Request resolved: facebook#51707 Currently, the feature flag system does not properly support non-boolean feature flags. The type definitions and generated code make assumptions about the value type being `boolean`. This diff fixes these assumptions so that non-boolean feature flags are supported. Changelog: [Internal] Differential Revision: D75690997
This pull request has been merged in 8343045. |
This pull request was successfully merged by @yungsters in 8343045 When will my fix make it into a release? | How to file a pick request? |
Summary:
Currently, the type definitions for feature flags assumes
boolean
values in theexpectedReleaseValue
field.This diff fixes them so
expectedReleaseValue
must match the type ofdefaultValue
.Changelog:
[Internal]
Differential Revision: D75690997