fix: Use clientSideAvailability instead of clientSide for filtering client side flags. #270
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lient side flags.
kinyoklion
requested review from
louis-launchdarkly and
yusinto
as code owners
louis-launchdarkly
approved these changes
Sep 6, 2023
kinyoklion
commented
Sep 6, 2023
| "usingEnvironmentId": true | ||
| "usingEnvironmentId": false | ||
| }, | ||
| "clientSide": false, |
Member
Author
There was a problem hiding this comment.
clientSide had been set false, but not usingEnvironmentId, these should be consistent.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The node-server-sdk was not using the newer
clientSideAvailability, butclientSide. In porting to TS that logic was retained. This updates it to use the newer field.