Salvatore Ravidà

Switch to redux-first-history: https://github.com/salvoravida/redux-first-history support react-router v6 and is issues-free!

Switch to redux-first-history: https://github.com/salvoravida/redux-first-history support react-router v6 and is issues-free!

> > Switch to redux-fist-history: https://github.com/salvoravida/redux-first-history support react-router v6 and is issues-free! > > Thanks! I'll play with it. 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...

@aandronache https://github.com/salvoravida/redux-first-history#options

Hi guys, the main problem of this package is that it handles syncronization via React Component Lyfecicles. this is the biggest mistake of this package, that have so over 100...

@brettjonesdev @RichardForrester @koyta Use https://github.com/salvoravida/redux-first-history No more location issue. 🎉

> > @brettjonesdev @RichardForrester @koyta > > Use https://github.com/salvoravida/redux-first-history > > No more location issue. > > Well, doesn't work for us. Same issue as with connected-router in terms of...

@momesana I m quite sure that there is something wrong with your code, not with redux first history. I will try to explain: back button or dispatch new url is...

@momesana ok, the problem is the states update top-down, because of selector update before `````` on this particular edge case (even if i think you should return null if the...