Slight refactor to partial hydration to leverage state.initialized properly #11094
Conversation
🦋 Changeset detectedLatest commit: 2b34fd0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
|
||
| // TODO: Probably want these running against RouterProvider in react-router too? | ||
| // Look into extracting the setState stuff and sharing the subscriber, | ||
| // layout effect, navigator, render stuff |
There was a problem hiding this comment.
Moved to partial-hydration-test and these now also run against the react-router RouterProvider along with createMemoryRouter
|
🤖 Hello there, We just published version Thanks! |
|
🤖 Hello there, We just published version Thanks! |
The previous approach felt wrong since we were hijacking initialized incorrectly.
state.initializedis back to meaning "do I need to run loaders during router.initialize()" and we use the future flag to bypass renderingfallbackElement