Fix broken proxy anchor in JS Session Replay data-residency link - #140
Draft
claude[bot] wants to merge 1 commit into
Draft
Fix broken proxy anchor in JS Session Replay data-residency link#140claude[bot] wants to merge 1 commit into
claude[bot] wants to merge 1 commit into
Conversation
Repoint the Data Residency link on the JS Session Replay page from the non-existent #self-hosted-proxy anchor to #tracking-via-proxy, and update the link text to match. Also repoint a stale docs.json legacy redirect from #how-to-set-up-a-proxy to #tracking-via-proxy.
Contributor
Confidence Score: 5/5The PR appears safe to merge. Both changes consistently replace stale anchors with the established
|
| Filename | Overview |
|---|---|
| docs.json | Updates a legacy redirect from a stale proxy anchor to the documented proxy section. |
| docs/tracking-methods/sdks/javascript/javascript-replay.mdx | Corrects the proxy documentation link and aligns its visible text with the destination heading. |
Reviews (1): Last reviewed commit: "Fix broken proxy anchor in JS Session Re..." | Re-trigger Greptile
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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.
Requested by Ross Gonsolvis · Slack thread
What & Why
The "Data Residency" section of the JavaScript Session Replay page had a link whose anchor matched no heading on the target page, so it silently dropped readers at the top of the JavaScript SDK page instead of the proxy setup instructions.
Before: In the Data Residency section, the "Self-Hosted Proxy" link pointed to
/docs/tracking-methods/sdks/javascript#self-hosted-proxy. No heading on the JavaScript SDK page slugs toself-hosted-proxy, so the anchor was dead and the link landed at the top of the page.After: The link points to
/docs/tracking-methods/sdks/javascript#tracking-via-proxy— the real "Tracking Via Proxy" section — and its visible text now reads "Tracking Via Proxy" to match the destination. The surrounding sentence still opens with "For self-hosted proxies," so the self-hosted context is preserved in prose. This is the same anchor four other pages already use.Second change: A legacy redirect in
docs.jsonpointed at another stale anchor,#how-to-set-up-a-proxy, which also no longer exists. It is repointed to#tracking-via-proxy.How
docs/tracking-methods/sdks/javascript/javascript-replay.mdx(line 36): changed the link text and anchor from[Self-Hosted Proxy](.../javascript#self-hosted-proxy)to[Tracking Via Proxy](.../javascript#tracking-via-proxy).docs.json(line 2948): changed the redirect destination anchor from#how-to-set-up-a-proxyto#tracking-via-proxy(source path unchanged).Target section verified at
docs/tracking-methods/sdks/javascript.mdx:950—## Tracking Via Proxy(Mintlify slugtracking-via-proxy).