fix: classify collapsed generated paths from child routes (#99864)
### What Fix the build route table so a collapsed generated-path row uses the shared symbol of the concrete paths it represents. The Maintainer Agent regression test now expects the Static symbol. ### Before The generated paths are static, but the collapsed row inherits the Partial Prerender symbol from the dynamic route pattern: ```text └ /blog/[...slug] ├ ◐ /blog/[...slug] ├ ○ /blog/post-1 ├ ○ /blog/post-2 └ ◐ [+10 more paths] ``` ### After The collapsed row uses the shared Static symbol from the generated paths it represents: ```text └ /blog/[...slug] ├ ◐ /blog/[...slug] ├ ○ /blog/post-1 ├ ○ /blog/post-2 └ ○ [+10 more paths] ``` The route pattern remains Partial Prerender because it can still handle paths outside `generateStaticParams`. Only the collapsed generated-path row changes. ### Why With Cache Components, Partial Prefetching, and `ensureStatic = 'navigation'`, a catch-all route can have a Partial Prerender route pattern while every generated path is complete and static. The synthetic `[+N more paths]` label has no `pageInfos` entry, so it previously fell back to the route pattern and printed Partial Prerender for those static paths. ### How Compute the hidden paths’ symbols in both the regular and duration-sorted truncation branches. Use the shared child symbol when every hidden path agrees; if the hidden paths have mixed symbols, preserve the conservative route-pattern fallback. The regression test asserts the real `next build` CLI output and verifies that every generated path produces complete static HTML. ### Documentation The Building guide introduces the collapsed `[+N more paths]` notation at first use and shows the correct symbol as the rendering classification changes. ### Validation - `NEXT_SKIP_ISOLATE=1 pnpm test-start-turbo test/e2e/app-dir/build-output-truncated-generated-paths/` — 2 passed - `NEXT_SKIP_ISOLATE=1 pnpm test-start-turbo test/production/build-output/build-output.test.ts` — 10 passed, 2 skipped - `pnpm --filter=next build` — passed - Pre-commit Prettier and ESLint checks passed - Prettier check for the documentation — passed Maintainer investigation: https://next-maintainer-agent.vercel.tools/investigations/feedback/64 DX Agent feedback: https://dxagent.labs.vercel.dev/dashboard/feedback/3fbc3904-2843-4eb6-9033-312f4306b66b Prepared in fork: https://github.com/vercel-labs/next.js-experimental/pull/237 --------- Co-authored-by:vercel-gh-bot-3[bot] <282332853+vercel-gh-bot-3[bot]@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment