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
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.
Cloudflare Assets can still emit same-path trailing-slash redirects for prerendered pages when website-router strips the
/graphql/hivemount before proxying upstream. That broke the real prod contract: raw upstream/and/docs/...had to resolve while still emitting/graphql/hive/...links.This keeps prerender first, but follows that one safe aliased asset redirect internally instead of exposing it. It also adds integration coverage for the real website-router contract: raw upstream
/and/docs/gatewaymust return HTML whose canonicals, nav links, and asset URLs stay/graphql/hive/....Tests:
bun --bun tsc --noEmitbun test src/server/cloudflare-routing.test.tsbun test src/routes/docs/-$.test.tsCI=true bunx playwright test e2e/landing-page.e2e.ts --project=chromium