Skip to content
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

Closed
filiptc opened this issue Sep 1, 2015 · 6 comments
Closed

_k parameter in route on v1.0.0-beta4 #1797

filiptc opened this issue Sep 1, 2015 · 6 comments

Comments

@filiptc
Copy link

filiptc commented Sep 1, 2015

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?

@malte-wessel
Copy link

react-router now uses rackt/history under the hood, have a look here Hash History Caveats.

@jdelight
Copy link

jdelight commented Sep 1, 2015

@filiptc I solved this by switching to browser history, something like:

import createHistory from 'history/lib/createBrowserHistory';
...
ReactDOM.render(<Router children={routes} history={createHistory()}/>, document.getElementById('b-main'));

@mjackson
Copy link
Member

mjackson commented Sep 3, 2015

Thanks for the link to the docs, @malte-wessel :)

@mjackson mjackson closed this as completed Sep 3, 2015
@ghost
Copy link

ghost commented Sep 8, 2015

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?

@ghost
Copy link

ghost commented Sep 8, 2015

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).

@Download
Copy link
Contributor

1.0 docs for future reference (this issue ranks high in Google)

@lock lock bot locked as resolved and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants