add react & js docs for feature flag setup #33281
Open
+501
−0
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
github-actions
bot
added
Architecture
Contributor
Preview links (active after the
|
Contributor
|
Created DOCS-12884 for documentation team review |
nothing wrong with these, but they are distracting in the diff
joepeeples
approved these changes
Dec 24, 2025
Contributor
joepeeples
left a comment
joepeeples
left a comment
There was a problem hiding this comment.
Added a couple comments to consider, thanks! This PR also seems to overlap with the "browser" SDK documented in #33445, but we can discuss that separately.
|
|
||
| ## Evaluate flags | ||
|
|
||
| Once the provider is initialized, you can evaluate flags anywhere in your application. Flag evaluation is _local and instantaneous_ - the SDK uses locally cached data, so no network requests occur when evaluating flags. |
Contributor
There was a problem hiding this comment.
Suggested change
| Once the provider is initialized, you can evaluate flags anywhere in your application. Flag evaluation is _local and instantaneous_ - the SDK uses locally cached data, so no network requests occur when evaluating flags. | |
| After the provider is initialized, you can evaluate flags anywhere in your application. Flag evaluation is _local and instantaneous_—the SDK uses locally cached data, so no network requests occur when evaluating flags. |
| } | ||
| {{< /code-block >}} | ||
|
|
||
| ## Updating the evaluation context |
Contributor
There was a problem hiding this comment.
Also, WDYT about moving this section to immediately follow "Set the evaluation context" since they seem related? It feels a little tacked onto the end of the page here.
Suggested change
| ## Updating the evaluation context | |
| ## Update the evaluation context |
| } | ||
| {{< /code-block >}} | ||
|
|
||
| ## Updating the evaluation context |
Contributor
There was a problem hiding this comment.
Same as comment above, consider moving this section to immediately follow "Set the evaluation context" since they seem related?
Suggested change
| ## Updating the evaluation context | |
| ## Update the evaluation context |
correct alt text in JavaScript tile in partial Co-authored-by: StefonSimmons <[email protected]>
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.
What does this PR do? What is the motivation?
Adds setup instructions for feature flags JavaScript & React SDKs.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes