bug-report - param containing double encoded characters should not be double decoded by useParams #13813
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.
It seems parameters which are encoded using
encodeURIComponent
are automatically decoded when usinguseParams
ormatchPath
.So if I encode them twice, I expect them to be encoded once, after calling
useParams
. However, it seems like there is something special with forward slash (/
). It is fully decoded after getting it withuseParams
, whereasmatchPath
works as expected.