There is a router (react-router). Did the integration of routing with Redux, and it turns out that, in order not to break the work of react-router, I have to dispatchit action ROUTE_CHANGE once the route has changed. In the code I implement this by listening for changes in browser history. In fact, the existing react-router-redux works the same, only less flexible and does not allow to pass parameters to state.
Further, since the dispatch ROUTE_CHANGE realized after the fact, it is very convenient to use the native means react-router, in particular, the component Redirect to in the right places to redirect, instead of the dispatch(push('/route')).
In fact, the essence of the issue: is this permissible? The sequence of events is the following: change of router > dispatch > update state. As far as I know, redux suggests a different priority: dispatch > change routes in response to dispatch > update state.