fix(react-rotuer): Fixed bug when using useSearchParams with useBlocker #12784
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.
Issue Overview
nextInit
, if thenextInit
implementation modifies properties using methods likedelete()
oradd()
. the internal property values ofsearchParams
change before thenavigate
function executes.useBlocker
hook, this can lead tosearchParams
values that don't match withlocation.search
(which is a dependency).Solution
searchParams
. This ensures that even ifsearchParams
values are modified in thenextInit
function, thesearchParams
within the hook remains unchanged.I have confirmed that issue #12256 has been resolved by implementing the exact solution specified in the issue description.
closes: #12256 #12188