Add copy button to hard-coded API docs#37628
Open
jhgilbert wants to merge 5 commits into
Open
Conversation
Contributor
Contributor
|
rtrieu
approved these changes
Jun 22, 2026
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
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?
Merge readiness
Adds a button to the hard-coded (non-generated) API docs. There are only four pages like this, all in the Overview section (example).
Note that CORS errors are expected in staging, since there is no staging plaintext build, so the Copy button fails over to the HTML scrape. But you can see that the URL of the failed request does exist (for example,
https://docs.datadoghq.com/api/latest.md), so it would work fine in prod, where the request would be coming from the same origin (docs.datadoghq.com).Also removes an unwanted underline on hover, the CSS just wasn't fleshed out enough on the original button.
If you're the docs reviewer, not much for you to do here, feel free to stamp it. I can seek CorpWeb approval myself, don't worry about escalating it for me.
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes