-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
feat: Client api dependent features #4778
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -17,20 +17,20 @@ export class DependentFeaturesService { | |||
} | |||
|
|||
async upsertFeatureDependency( | |||
parentFeature: string, | |||
childFeature: string, |
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.
it was a mistake in previous PR
.expect('Content-Type', /json/) | ||
.expect(200) | ||
.expect((res) => { | ||
expect(res.body.features[0]).toMatchObject({ |
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.
this is the basis for the client spec for SDKs
@@ -195,6 +201,16 @@ export default class FeatureToggleClientStore | |||
) { | |||
this.addSegmentIdsToStrategy(feature, r); | |||
} | |||
if (r.parent && !isAdmin && dependentFeaturesEnabled) { |
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.
we don't want to touch admin API in this PR, only client API to start SDK work
About the changes
Client API support for dependent feature toggles.
Important files
Discussion points