HPC-9975 Remove use-query-params
#481
Open
+257
−328
Conversation
This file contains 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
Onitoxan
added
the
ready for review
Onitoxan
changed the title
use-query-params
unocha-hpc
approved these changes
Dec 16, 2024
unocha-hpc
approved these changes
Dec 19, 2024
It's built on top of `useSearchParams` from `react-router`.
unocha-hpc
approved these changes
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Nature of PR
Description
This PR is related to HPC-9965, read for more context.
In this PR we focus on removing
use-query-paramspackage. It became obsolete since with the use ofreact-routerdata API hooks (precisely,useSearchParams()) and usingio-tsto write runtime validation, we can achieve the same objective.We do this in order to reduce dependency of external libraries.
How to test changes
To test changes I would try to manipulate the URL to see how it reacts even to unexpected
paramsand with wrong data on it.Beside this, I would focus mainly on reading logic for
useQueryParams()to verify it really covers corner cases