feat(react-router): Register a route provider backed by resolved routes - #23787
Closed
logaretm wants to merge 1 commit into
Closed
feat(react-router): Register a route provider backed by resolved routes#23787logaretm wants to merge 1 commit into
logaretm wants to merge 1 commit into
Conversation
The Data Router exposes matches only through router state, and the package has no runtime dependency on `react-router` to call `matchRoutes` with, so the provider answers from routes already resolved rather than by matching. Splits `getMatchedRoute` out of `getParameterizedRoute` so the provider can tell a matched route from the raw-pathname fallback, and records from both the hydrated router subscription and the instrumentation API, since each resolves routes the other never sees.
5 tasks
Contributor
size-limit report 📦
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Registers a route provider for React Router framework mode.
The Data Router exposes its matches only through router state, and the package has no runtime dependency on
react-routerto callmatchRouteswith, so the provider answers from routes already resolved rather than by matching.Reuses
getRouteTemplate(exported for this) rather than reading the leaf match, since nested routes carry paths relative to their parent and index and layout routes carry none. Records from both the hydrated router subscription and the instrumentation API, since each resolves routes the other never sees.Part of #23556