HashRouter and location.search #9459
Unanswered
eugenehuangsg
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Why do HashRouter useNavigate append the query string after the hash segment? (eg. localhost/#myroute?myquery=1). Isn't the expected format for URL supposed to be query string first then hash?
We have a use case where a third-party library reads the query string directly but because the current behaviour is that query string is part of hash, there are no values attached to location.search for it to be read. Is there a workaround for this?
Beta Was this translation helpful? Give feedback.
All reactions