Fix basename duplication in RouterProvider descendant routes #10492
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.
BrowserRouter
,useNavigateUnstable
will handle resolving the relative path and prepending the basenameRouterProvider
, therouter.navigate
will handle resolving relative paths and prepending the basenameHowever, If you use
RouterProvider
and include some descendant<Routes>
inside the tree, then that needs to useuseNavigateUnstable
to resolve relative paths but it should not also prepend the basename since navigation will still go throughrouter.navigate
Closes #10467