feat: Always inline contexts for feature events #351
Merged
Conversation
This file contains 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
keelerm84
requested review from
kinyoklion,
yusinto and
louis-launchdarkly
as code owners
|
This pull request has been linked to Shortcut Story #223829: Inline contexts for evals events. |
|
Do we need to change what harness version we are using? Or we will just be holding this PR until some time where we can re-run that? |
We will be able to use the v2 release for the test harness. But I'm still making changes as I work through the different types of SDKs so I've just been checking things locally. And since I've been making these PRs against a separate feature branch, I haven't been too worried about the failure in CI. I'm far enough along at this point that once the current PRs are merged, I can probably just cut a v2 release. |
kinyoklion
approved these changes
Feb 1, 2024
keelerm84
added a commit
that referenced
this pull request
Mar 13, 2024
keelerm84
added a commit
that referenced
this pull request
Mar 15, 2024
Merged
keelerm84
pushed a commit
that referenced
this pull request
Mar 15, 2024
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 1.1.1</summary> ## [1.1.1](akamai-edgeworker-sdk-common-v1.1.0...akamai-edgeworker-sdk-common-v1.1.1) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.2.0 to ^2.2.1 </details> <details><summary>akamai-server-base-sdk: 2.1.1</summary> ## [2.1.1](akamai-server-base-sdk-v2.1.0...akamai-server-base-sdk-v2.1.1) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^1.1.0 to ^1.1.1 * @launchdarkly/js-server-sdk-common bumped from ^2.2.0 to ^2.2.1 </details> <details><summary>akamai-server-edgekv-sdk: 1.1.1</summary> ## [1.1.1](akamai-server-edgekv-sdk-v1.1.0...akamai-server-edgekv-sdk-v1.1.1) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^1.1.0 to ^1.1.1 * @launchdarkly/js-server-sdk-common bumped from ^2.2.0 to ^2.2.1 </details> <details><summary>cloudflare-server-sdk: 2.4.1</summary> ## [2.4.1](cloudflare-server-sdk-v2.4.0...cloudflare-server-sdk-v2.4.1) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.2.0 to 2.2.1 </details> <details><summary>js-client-sdk-common: 1.0.2</summary> ## [1.0.2](js-client-sdk-common-v1.0.1...js-client-sdk-common-v1.0.2) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.2.0 to 2.3.0 </details> <details><summary>js-sdk-common: 2.3.0</summary> ## [2.3.0](js-sdk-common-v2.2.0...js-sdk-common-v2.3.0) (2024-03-15) ### Features * Always inline contexts for feature events ([#351](#351)) ([961d21b](961d21b)) * Redact anonymous attributes within feature events ([#352](#352)) ([8f7ad7e](8f7ad7e)) </details> <details><summary>js-server-sdk-common: 2.2.1</summary> ## [2.2.1](js-server-sdk-common-v2.2.0...js-server-sdk-common-v2.2.1) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.2.0 to 2.3.0 </details> <details><summary>js-server-sdk-common-edge: 2.2.1</summary> ## [2.2.1](js-server-sdk-common-edge-v2.2.0...js-server-sdk-common-edge-v2.2.1) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.2.0 to 2.2.1 </details> <details><summary>node-server-sdk: 9.2.1</summary> ## [9.2.1](node-server-sdk-v9.2.0...node-server-sdk-v9.2.1) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.2.0 to 2.2.1 </details> <details><summary>node-server-sdk-dynamodb: 6.1.3</summary> ## [6.1.3](node-server-sdk-dynamodb-v6.1.2...node-server-sdk-dynamodb-v6.1.3) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.2.0 to 9.2.1 * peerDependencies * @launchdarkly/node-server-sdk bumped from 9.2.0 to 9.2.1 </details> <details><summary>node-server-sdk-redis: 4.1.3</summary> ## [4.1.3](node-server-sdk-redis-v4.1.2...node-server-sdk-redis-v4.1.3) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.2.0 to 9.2.1 * peerDependencies * @launchdarkly/node-server-sdk bumped from 9.2.0 to 9.2.1 </details> <details><summary>react-native-client-sdk: 10.0.3</summary> ## [10.0.3](react-native-client-sdk-v10.0.2...react-native-client-sdk-v10.0.3) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.0.1 to 1.0.2 </details> <details><summary>vercel-server-sdk: 1.3.2</summary> ## [1.3.2](vercel-server-sdk-v1.3.1...vercel-server-sdk-v1.3.2) (2024-03-15) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.2.0 to 2.2.1 </details> --- 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: Ryan Lamb <4955475+kinyoklion@users.noreply.github.com>
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.
No description provided.