-
Notifications
You must be signed in to change notification settings - Fork 14
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
ClientLib changes for featureFlags to getKeys #1585
Conversation
…tConditionsRequestBody
experiment: ExperimentAssignmentValidator | ||
): Promise<string[]> { | ||
const experimentUserDoc = await this.experimentUserService.getUserDoc(experiment.userId, request.logger); | ||
return this.featureFlagService.getKeys(experimentUserDoc, experiment.context, request.logger); |
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 should return 404 when the user is not found, like with experiment assignment (and the removed 'keys' endpoint).
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.
will spawn task to keep the discussion going on Ben's comment
In this Pull Request, the ClientLib
getFeatureFlags
method invokesgetAllFeatureFlags
, which returns an array of feature flags associated with the key user. ThegetFeatureFlags
method then returns true or false based on whether the specified feature-flag key is present in the array.