-
Notifications
You must be signed in to change notification settings - Fork 1
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
Issue/vcs toggle vcs modes #352
Conversation
🦋 Changeset detectedLatest commit: bba2fe6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 99 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -27,6 +28,12 @@ export function getFeatureFlag(flagName: $Keys<FeatureFlags>): boolean { | |||
return value === true || value === 'NEW'; | |||
} | |||
|
|||
export function getFeatureFlagValue( |
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.
@yamadapc we can't use the existing getFeatureFlag
as we need to differentiate between NEW_AND_CHECK
and NEW
77962ce
to
e7a2eaf
Compare
We want to implement a consistency check pattern to enable VCS modes under a feature flag. There are 4 different scenarios that will be controlled by combining a 'killswitch', already implemented in product, and a flag to toggle the relevant mode, as explains below:
The first 2 modes are already available in the products and are switched on/off by an infra ff. This PR introduces the ability to return different values for the last 2 modes through another infra ff.