mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
Andrew ClarkandGitHub
8980f3a76a
When optimistic routing is enabled, the client uses responses it receives from the server (during a navigation or a prefetch) to resolve the routes of structurally similar URLs. However, if the server rewrites a URL to a different path than the one requested by the client, then we disable optimistic routing for that pattern. We detect a rewrite by comparing the route tree returned from the server to the requested URL. If the route tree does not match, according to the Next.js routing algorithm, then the route must have been rewritten; we do not write this pattern into the client's route table. The basic mechanism for this was already implemented, but there were some cases we weren't handling correctly: - A static or non-optional dynamic segment is reached with no URL part to consume. - A page leaf is reached with URL parts still pending. - A dynamic segment whose URL part matches one of its known static siblings (which would have taken precedence under normal routing). These cases have been fixed. Regression tests live in `optimistic-routing-rewrite-detection-regression/` and `optimistic-routing-parallel-slot-catchall-regression/`. --- Replaces #93578 (re-opened from an `origin` branch to satisfy CI requirements).
14 lines
560 B
TypeScript
14 lines
560 B
TypeScript
// The real /featured static page. At runtime the `beforeFiles` rewrite
|
|
// hijacks /featured requests and sends them through /[teamSlug], so this
|
|
// page is never actually served — but its presence on the filesystem
|
|
// matters: it makes /featured a static sibling of /[teamSlug], which is
|
|
// what makes the rewrite case observable to the router (a request for
|
|
// /featured could not have arrived at /[teamSlug] under normal routing).
|
|
export default function FeaturedPage() {
|
|
return (
|
|
<main>
|
|
<h1 id="featured-page">FEATURED</h1>
|
|
</main>
|
|
)
|
|
}
|