fix(useRouteQuery,useRouteParams): prevent reset on other scope dispose #3418
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.
Before submitting the PR, please make sure you do the following
fixes #123
).Description
Fix #3360
Additional context
🤖 Generated by Copilot at 82eb049
This pull request improves the performance and reliability of the
useRouteParams
anduseRouteQuery
functions by using weak maps to store router-specific state instead of global caches. It also adds and fixes some test cases for these functions to verify their behavior.🤖 Generated by Copilot at 82eb049
useRouteParams
anduseRouteQuery
functions to use router-specific queues instead of global caches (link,link,link,link,link,link,link,link)useRouteParams
anduseRouteQuery
to check that they are not reset to default value when scope is disposed from another scope (link,link,link)useRouteQuery
(link)