-
Notifications
You must be signed in to change notification settings - Fork 592
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
@@router/LOCATION_CHANGE fires twice #4
Comments
Actually, I don't understand the purpose of calling syncHistoryWithStore(history, store). |
Yes. You're right. |
Thanks! |
@bazalev Already fixed in v1.0.0-alpha.5! |
Awesome! |
Hello @supasate , sorry for taggin in such an old issue. But I am migrating from How do I convert this part to work? |
I still see this issue. I have bootstrapped application using redux-toolkit and eventually added connected-react-router for syncing redux store with router location. I see LOCATION_CHANGE firing twice every time Link is clicked. I tried "push" also by converting Link to a Button, but that also fired it twice. Is this an issue? |
I am having this issue... |
I am also having the same issue, LOCATION_CHANGE is getting fired twice with the connected-react-router v6.8.0 |
@ruchirV @ibocon @pranjul-sharma guys you probably wrapped your code inside index.js/tsx using |
This is right. I've also noticed that reverting an |
I've found that moving It's not perfect but better than before.
|
The first listener subscribes in syncHistoryWithStore and the second in ConnectedRouter constructor.
Is it correct to fire this action twice on each transition?
The text was updated successfully, but these errors were encountered: