-
Notifications
You must be signed in to change notification settings - Fork 0
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-side prerequisite events #24
Conversation
c2c1e53
to
9fd6707
Compare
7ac50b0
to
8a6d14b
Compare
{ | ||
prerequisites ??= new List<string>(); | ||
prerequisites.Add(reader.GetString()); | ||
} |
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.
Doing the null coalescing operator because otherwise, we'd potentially construct an empty prereq array if the JSON value is null.
Noting that the Server SDK big segments tests failed, as well as the contract tests at one point (but passed upon re-run). These changes are entirely to the Client SDK, so I'm going to merge anyways. |
🤖 I have created a release *beep* *boop* --- ## [5.3.0](LaunchDarkly.ClientSdk-v5.2.1...LaunchDarkly.ClientSdk-v5.3.0) (2024-10-31) ### Features * client-side prerequisite events ([#24](#24)) ([f5828cb](f5828cb)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Allows the client SDK to deserialize
prerequisites
from the flag model and then emit prerequisite evaluation events.