mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
Josh StoryandGitHub
e2b0d2eadc
The error message previously did not say which parallel route slot couldn't be validated. Now it poitns to the nearest segment below the validation boundary. The idea is you go look abive this and figure out if it is intentional that this segment isn't rendered in the current context. If so you can ignored the warning (it should ideally not even be presented as a normal error) but if it is unintentional you investigate why you aren't SSRing this slot or you mark the slot as intentionally blocking so it doesn't get validated.
13 lines
404 B
TypeScript
13 lines
404 B
TypeScript
// No config. Hides {children} to trigger the missing-boundary fallback.
|
|
// The config lives deeper (inner/leaf/page.tsx), but this layout is
|
|
// what prevents it from rendering.
|
|
import { ReactNode } from 'react'
|
|
|
|
export default function Layout({ children }: { children: ReactNode }) {
|
|
return (
|
|
<main>
|
|
<p>test-firstmod root layout — children intentionally not rendered</p>
|
|
</main>
|
|
)
|
|
}
|