-
Notifications
You must be signed in to change notification settings - Fork 593
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
Support react router 6 #543
Comments
Looks like #438 is aimed at doing that but has been left alone, I may apply that as a patch to the latest version myself to resolve the immediate issue |
Switch to redux-first-history: https://github.com/salvoravida/redux-first-history |
Thanks! I'll play with it. |
@Iuriy-Budnikov Could you write after your result after migrate |
Great, looking forward to your feedback! |
@salvoravida @Iuriy-Budnikov I moved to redux-first-history and all good works as excepted. Migration was smooth. |
update to 5.0.2 that fixes support for react-router 6.0.2 while waiting for this official Pull Request remix-run/react-router#7586 let me know your feedback! |
@salvoravida Updated to 5.0.2 and react router 6.0.2 all good |
Same as #397 |
Hey @salvoravida, |
I have the same problem, I think it does not support react-router V6 |
I have a same problem ant that case is with interfaces.
Problem that extending
|
Just tried it now, It's great and loved the clear guides ❤️! |
@lovewinders @zygimantas-gylys You can try https://github.com/lagunovsky/redux-react-router API like for the |
This PR is in preparation of upgrading `react-router` inside of `fusion-plugin-react-router` to 6.x. `connected-router` does not support react-router 6 and going by the github repo commits and issues, they have no plans to. See supasate/connected-react-router#543. Seems like community members are migrating to other solutions. In lieu of this, this PR pins this plugin to the latest version of `fusion-plugin-react-router` to serve as a time capsule for whomever still wants to use this. That way when we upgrade `fusion-plugin-react-router` it won't break this plugin. Alternatively, there is potential work to migrate this plugin to use something else under the hood that supports react router 6 but to me that should be an entirely new plugin instead of continuing to work on this one.
@supasate is it fair to assume there will be no updates to this package going forward? |
After some agonizing, I discovered that the latest version of react-router-dom (v6) is supported by redux-first-history Connected-react-router seems to have not been maintained to support react-router v6: supasate/connected-react-router#543
New React/Redux project here totally dependent on |
Hi everyone, I'm still strugling myself on this Cannot read properties of undefined (reading 'pathname') console error. Does anyone can help me please ? |
The PR has been created 1 year ago. WTF ? #438 |
Do you have any plans to support 6 version? Do you need any help?
https://reactrouter.com
The text was updated successfully, but these errors were encountered: