-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_k parameter in route on v1.0.0-beta4 #1797
Comments
react-router now uses rackt/history under the hood, have a look here Hash History Caveats. |
@filiptc I solved this by switching to browser history, something like:
|
Thanks for the link to the docs, @malte-wessel :) |
Could you please elaborate on what's required to use BrowserHistory? I've been trying various ways to get this w/o success. I.e., we have to explicitly import this from the 'history' package? |
I'm guessing that my confusion was mainly from the doc showing an import of 'react-router/lib/HashHistory'. The comment above that line indicates importing only the function needed, which makes more sense (i.e., 'history/lib/createBrowserHistory' in my case). |
1.0 docs for future reference (this issue ranks high in Google) |
We just updated to beta4 and the param _k=6wznho corresponding to the location.key shows appears to show up in every route.
Is this a bug or is there a to-be-documented feature to disable this?
The text was updated successfully, but these errors were encountered: