LayoutRouter: Support segment value of Promise<null> to asynchronously bail out and trigger a server patch #59724
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the data for a segment is missing when LayoutRouter renders, it initiates a lazy fetch to patch the cache. This is how all dynamic data fetching works in the pre-PPR implementation.
For PPR, we won't use this mechanism anymore for regular navigations, but (at least for now) we will still use it as a fallback behavior if the server response does not match what we expected to receive.
This commit adds support for asynchronously triggering a lazy fetch, by unwrapping the segment data promise inside LayoutRouter to check if it's missing. If so, it will trigger the lazy fetch mechanism.
When PPR is not enabled this should not observably impact behavior.
Closes NEXT-1893