mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
Josh StoryandGitHub
938c286bac
When instant UI validation cannot successfully complete at a given simluated navigation level it previously would halt the validation there and report the error. This is fine however it is possible that the cause of the impcomplete validation is mundane (i.e. conditionally rendering a slot) and focussing on this lack of ability fully validate a level when other simulated navigations might also provide insights means we might send you down the wrong line of investigation when something more actionable already exists. In the long run these insights ought to be provided through a non-error UI. in that world we'd probably want to perform all the validations to their extent and then simply notify you about which ones could and could not be completed. However since we currently use the error overlay to convey these issues we will favor instead showing actionable errors from any validation depth before showing you less actionable "could not validate" errors
6 lines
224 B
TypeScript
6 lines
224 B
TypeScript
// Landing page for the multi-depth-deferred-fallback fixture. Not
|
|
// targeted by the deferral test — only present so the route exists.
|
|
export default function Page() {
|
|
return <p>multi-depth-deferred-fallback root</p>
|
|
}
|