Accepted answer

The way I think about it, the path is just a coarse reflection of the UI state of the app. The structure of the UI triggers from the path, via React Router, but the state should be in Redux. I should be able to recover the UI state by typing in the same path, and the path should change in recognition of major changes of UI state.

So basically, you want to change the router when you want to set a "checkpoint" or reconfigure your layout, but you still need to dispatch actions to change the state of the Redux store.

Related Query

More Query from same tag