IMO, the right place to sort data is not directly in the reducers but in the selectors. From redux docs: Computing Derived Data Reselect is a simple library for creating memoized, composable selector functions. Reselect selectors can be used to efficiently compute derived data from the Redux store. I’m currently using selectors to filter and … Read more
Definitely persist the state of your reducers! If you persisted a sequence of actions instead, you wouldn’t ever be able to modify your actions in your frontend without fiddling around inside your prod database. Example: persist one reducer’s state to a server We’ll start with three extra action types: // actions: ‘SAVE’, ‘SAVE_SUCCESS’, ‘SAVE_ERROR’ I … Read more
With React Router 2+, wherever you dispatch the action, you can call browserHistory.push() (or hashHistory.push() if that’s what you use): import { browserHistory } from ‘react-router’ // … this.props.dispatch(registerStep1Success()) browserHistory.push(‘/registrationStep2’) You can do this from async action creators too if that is what you use.
There is no way to subscribe to part of the store when using subscribe directly, but as the creator of Redux says himself – don’t use subscribe directly! For the data flow of a Redux app to really work, you will want one component that wraps your entire app. This component will subscribe to your … Read more
I would suggest just using React Router directly and not keeping searchState in Redux. React Router will inject URL parameters into your components, and you can use them in mapStateToProps(state, ownProps) to calculate the final props. If you really want to see route changes as actions, you can use react-router-redux for two-way syncing, but it … Read more