feat(developer): redirect legacy docs URLs to guides - #958
kevincador wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
vladjerca
left a comment
There was a problem hiding this comment.
Checked out and ran the portal gate: deno fmt --check, prettier check, deno task check (0 errors with the PUBLIC_* vars set), deno task test (46 files, 250 tests) and deno task build all pass. The build emits the 404.html fallback the shim relies on.
The spec covers all 24 guides against contents.md, both aliases, trailing slash and .md variants, and the unknown-path fallback (including /docs/constructor, which the Map lookup handles). Nothing to fold, so I left the branch untouched.
Reminder from the description: the hostname redirect still needs configuring separately, otherwise the shim never sees the old URLs.
Map legacy
/docs/*URLs to their corresponding developer portal guides after the hostname redirect preserves the original path.For example,
/docs/caching-and-fresh-metadataopens/?section=guides&guide=caching-and-fresh-data.Covers 24 docs pages and two aliases, including trailing slashes and
.mdURLs. Unknown paths fall back to the homepage. Reference pages have no dedicated mappings.The shim runs in the browser through the existing GitHub Pages 404 fallback. The hostname redirect must be configured separately.