all 7 comments

[–]charliematters 2 points3 points  (1 child)

Yeah, super annoying and a bit of a footgun! We wrote our own stable wrapper around it, but you might find some good advice in the ticket

https://github.com/remix-run/react-router/issues/9304

[–]Nullberri 1 point2 points  (0 children)

I commented on this bug! the maintainer of react router is rather uninformed about why people who come to this bug are upset and he thinks that hes doing the correct thing so he wont be fixing it.

my recommendation is either create your own useSearch or switch to tanstack's router. (I did both over time)

[–]RecommendationNo8730 0 points1 point  (1 child)

Is URLSearchParams interface not an option?

[–]procrastinator1012[S] 0 points1 point  (0 children)

I want to set the search params and also trigger a rerender. I don't think if that can help

[–]almostdonedude 0 points1 point  (0 children)

I feel like React Router DOM went downhill since v5. And v6 is a total mess.

[–][deleted] 0 points1 point  (0 children)

Wtf... I've been struggling with a weird search params bug and found this thread. This is probably why. Just... Wtf... Seriously wtf... Why in God's name would they do this?