chore(ui): exports parseSearchParams #10185
Merged
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.
As pointed out in #10164, parsing a
where
query from search params is not exactly straightforward. Internally we rely on theqs
module for this, but it comes with a couple small nuances that are undocumented, like the need to stringify them and specify depth. To standardize this, we use aparseSearchParams
utility internally that accepts theURLSearchParams
object that theuseSearchParams()
hook returns fromnext/navigation
. This PR exports that function for reuse and adds JSDocs accordingly. Usage looks something like this: