Skip to content

ref: Replace useUrlParams in favor of nuqs#112268

Merged
ryan953 merged 10 commits intomasterfrom
ryan953/rm-useUrlParams
Apr 6, 2026
Merged

ref: Replace useUrlParams in favor of nuqs#112268
ryan953 merged 10 commits intomasterfrom
ryan953/rm-useUrlParams

Conversation

@ryan953
Copy link
Copy Markdown
Member

@ryan953 ryan953 commented Apr 6, 2026

Related to https://github.com/getsentry/frontend-tsc/issues/78, we shouldn't be using browserHistory anymore: useNavigate() covers cases where we want to change it, and location/nuqs covers reading and query-params too.

So this aims to remove useUrlParams from the codebase, it's a query-param helper that is basically a bad version of nuqs. We can use nuqs instead.

Related to https://github.com/getsentry/frontend-tsc/issues/78

@ryan953 ryan953 requested review from a team as code owners April 6, 2026 17:48
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 6, 2026
@ryan953 ryan953 merged commit 266c806 into master Apr 6, 2026
74 checks passed
@ryan953 ryan953 deleted the ryan953/rm-useUrlParams branch April 6, 2026 20:56
george-sentry pushed a commit that referenced this pull request Apr 9, 2026
Related to getsentry/frontend-tsc#78, we
shouldn't be using browserHistory anymore: `useNavigate()` covers cases
where we want to change it, and location/nuqs covers reading and
query-params too.

So this aims to remove `useUrlParams` from the codebase, it's a
query-param helper that is basically a bad version of nuqs. We can use
nuqs instead.

Related to getsentry/frontend-tsc#78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants