-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(router): fallback support in new_defineRouter and new_createPages #1013
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems fine. I don't yet fully understand what fallbackElement
is yet though.
}>; | ||
}): ReturnType<typeof defineEntries> { | ||
const platformObject = unstable_getPlatformObject(); | ||
type MyPathConfig = { | ||
pattern: string; | ||
pathname: PathSpec; | ||
// FIXME Do we need this isStaticRouteElement? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope! good catch, safe to remove. This just slipped in as left over
// HACK I'm not sure if this is the right way | ||
return createElement( | ||
ChildrenContextProvider, | ||
{ value: createElement(InnerErr, { err }) }, | ||
fallback, | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this hack works for new_createPages fallback. Let check it after merging...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't work. so #1015.
if (unstable_renderPrev) { | ||
if (!elementsPromise.prev) { | ||
throw new Error('Missing prev elements'); | ||
} | ||
return renderSlot(elementsPromise.prev); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not happy with this, and hope to redesign it after finishing our current transition.
add fallback mechanism for #1003.