connected-react-router VS redux-auth-wrapper

connected-react-router : Helps to connect your route with the redux state.

So, I think many people are not familiar with the concept of integrating a router into the Store, but in fact they most likely met the Connected React Router library, it allows, for example, with successful authentication directly in the action, to redirect the user to the /profile or /dashboard page, this allows the authentication logic do not spread beyond the action. To begin with, we will write timings for the state of this store.

Even if I look at the basic example on their GitHub, there is a similar coding pattern.

For this use case, I would use https://github.com/supasate/connected-react-router to make it so changing the state is changing the URL and then just having a link action fire a navigation action.

Info on setting up linking and routing to pages: https://github.com/supasate/connected-react-router/blob/master/FAQ.md#how-to-navigate-with-redux-action

Connect react-router with redux: https://github.com/supasate/connected-react-router This will allow you to navigate via dispatching actions from the saga.

redux-auth-wrapper: A higher order component sounds great but I still cannot figure out how to integrate it without any dedicated Login component.