-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(flags): Add browser JS integration docs for Launchdarkly #11839
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
Conversation
…chdarkly…" This reverts commit 39f14ed.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will increase total bundle size by 258 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
|
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.
Thanks for adding!
@@ -0,0 +1,54 @@ | |||
--- | |||
title: LaunchDarkly | |||
description: "Attaches recent LaunchDarkly feature flag evaluations to error event context." |
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.
description: "Attaches recent LaunchDarkly feature flag evaluations to error event context." | |
description: "Learn how to attach LaunchDarkly feature flag evaluations to error event context." |
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.
@cmanallen Should this be expanded to feature flag change tracking?
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.
Is this too verbose? "Learn how to attach recent LaunchDarkly feature flag evaluations to your error event context"
@cmanallen Should this be expanded to feature flag change tracking?
@jas-kas The SDK integration doesn't track FF changes, only evaluations leading up to the error. Changes are tracked through the webhook, maybe we can link the docs for that
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.
^ basically +1 to Michelle's comment below!
|
||
The [LaunchDarkly](https://launchdarkly.com/) integration tracks feature flag evaluations produced by the LaunchDarkly SDK. These evaluations are held in memory and, in the event an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.** |
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.
The [LaunchDarkly](https://launchdarkly.com/) integration tracks feature flag evaluations produced by the LaunchDarkly SDK. These evaluations are held in memory and, in the event an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.** | |
The [LaunchDarkly](https://launchdarkly.com/) integration tracks feature flag evaluations produced by the LaunchDarkly SDK. These evaluations are held in memory and, if an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.** |
Learn more about the LaunchDarkly SDK at https://docs.launchdarkly.com/sdk/client-side/javascript. | ||
At the moment, **we do not officially support framework-specific LaunchDarkly | ||
SDKs.** However, you may reuse this setup code for React and client-side Node.js. |
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.
Learn more about the LaunchDarkly SDK at https://docs.launchdarkly.com/sdk/client-side/javascript. | |
At the moment, **we do not officially support framework-specific LaunchDarkly | |
SDKs.** However, you may reuse this setup code for React and client-side Node.js. | |
Learn more about the [LaunchDarkly SDK] (https://docs.launchdarkly.com/sdk/client-side/javascript). | |
At the moment, **we don't officially support framework-specific LaunchDarkly | |
SDKs.** However, you can reuse this setup code for React and client-side Node.js. |
## Options | ||
|
||
There are no setup options for this integration. |
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.
## Options | |
There are no setup options for this integration. | |
## Options | |
There are no setup options for this integration. |
Same comment as for open feature - maybe it's best to delete this section?
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.
I left it in so we'd remember to update it if we add options in the future. Don't have strong opinions on this though
Should we also include this step right here on this docs page https://github.com/getsentry/sentry-docs/pull/11971/files#r1863929949? |
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.
Looks good! Main comment is should we expand this to talk about set up for feature flag change tracking, not just evaluation?
@@ -0,0 +1,54 @@ | |||
--- | |||
title: LaunchDarkly | |||
description: "Attaches recent LaunchDarkly feature flag evaluations to error event context." |
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.
@cmanallen Should this be expanded to feature flag change tracking?
|
||
<Alert level="info"> | ||
|
||
This integration only works inside a browser environment. |
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.
Should we re-frame this to just call out JavaScript and Python as supported SDKs?
looks like this got pulled into the big docs PR here: https://github.com/getsentry/sentry-docs/pull/12005/files#diff-3365be2e16bf22c9c585399fe09132f3aaaa952585587745a54a0f114dfbc7fb closing this so we can focus there. |
Re-adds LaunchDarkly integration documentation.
Reverts #11838