React Redux
Official React bindings for Redux.
Performant and flexible.
![redux channel on slack](https://img.shields.io/badge/slack-redux@reactiflux-61DAFB.svg?style=flat-square)
Note: There is a project called redux-react
on NPM that is completely unrelated to the official bindings. This documentation (and any other official Redux documentation) is for react-redux
.
Table of Contents
React Native
What you get from react-redux
is for React.
For React Native, import from react-redux/native
instead.
Quick Start
React bindings for Redux embrace the idea of dividing “smart” and “dumb” components.
It is advisable that only top-level components of your app (such as route handlers, for example) are aware of Redux. Components below them should be “dumb” and receive all data via props.
| Location | Use React-Redux | To read data, they | To change data, they |
---|
“Smart” Components | Top level, route handlers | Yes
| Subscribe to Redux state | Dispatch Redux actions |
“Dumb” Components | Middle and leaf components | No
| Read data from props | Invoke callbacks from props |
“Dumb” component is unaware of Redux
Let’s say we have a <Counter />
“dumb” component with a number value
prop, and an onIncrement
function prop that it will call when user presses an “Increment” button:
import { Component } from 'react';
export default class Counter extends Component {
render() {
return (
<button onClick={this.props.onIncrement}>
{this.props.value}
</button>
);
}
}
“Smart” component is connect()
-ed to Redux
Here’s how we hook it up to the Redux Store.
We will use connect()
function provided by react-redux
to turn a “dumb” Counter
into a smart component. The connect()
function lets you specify which exactly state from the Redux store your component wants to track. This lets you subscribe on any level of granularity.
containers/CounterContainer.js
import { Component } from 'react';
import { connect } from 'react-redux';
import Counter from '../components/Counter';
import { increment } from '../actionsCreators';
function mapStateToProps(state) {
return {
value: state.counter
};
}
function mapDispatchToProps(dispatch) {
return {
onIncrement: () => dispatch(increment())
};
}
export default connect(
mapStateToProps,
mapDispatchToProps
)(Counter);
Whether to put connect()
call in the same file as the “dumb” component, or separately, is up to you.
Ask yourself whether you'd want to reuse this component but bind it to different data, or not.
Nesting
You can have many connect()
-ed components in your app at any depth, and you can even nest them. It is however preferable that you try to only connect()
top-level components such as route handlers, so the data flow in your application stays predictable.
Support for Decorators
You might have noticed that we used parens twice. This is called partial applications, and it lets people
use ES7 decorator proposal syntax:
@connect(mapStateToProps)
export default class CounterContainer { ... }
Don’t forget decorators are experimental! And they desugar to function calls anyway as example above demonstrates.
Additional Flexibility
This the most basic usage, but connect()
supports many other different patterns: just passing the vanilla dispatch()
function down, binding multiple action creators, putting them as actions
prop, selecting parts of state and binding action creators depending on props
, and so on. Check out connect()
docs below to learn more.
Injecting Redux Store
Finally, how do we actually hook it up to a Redux store? We need to create the store somewhere at the root of our component hierarchy. For client apps, the root component is a good place. For server rendering, you can do this in the request handler.
The trick is to wrap the whole view hierarchy into <Provider>{() => ... }</Provider>
where Provider
is imported from react-redux
. One gotcha is that the child of Provider
must be a function. This is to work around an issue with how context (undocumented feature we have to rely on to pass Redux data to components below) works in React 0.13. In React 0.14, you will be able to put your view hierarchy in <Provider>
without wrapping it into a function.
import { Component } from 'react';
import { Provider } from 'react-redux';
class App extends Component {
render() {
}
}
const targetEl = document.getElementById('root');
React.render((
<Provider store={store}>
{() => <App />}
</Provider>
), targetEl);
API
<Provider store>
Makes Redux store available to the connect()
calls in the component hierarchy below.
You can’t use connect()
without wrapping the root component in <Provider>
.
Props
store
: (Redux Store): The single Redux store in your application.children
: (Function): Unlike most React components, <Provider>
accepts a function as a child with your root component. This is a temporary workaround for a React 0.13 context issue, which will be fixed when React 0.14 comes out.
Example
Vanilla React
React.render(
<Provider store={store}>
{() => <MyRootComponent />}
</Provider>,
rootEl
);
React Router 0.13
Router.run(routes, Router.HistoryLocation, (Handler, routerState) => {
React.render(
<Provider store={store}>
{() => <Handler routerState={routerState} />} // note "routerState" here: important to pass it down
</Provider>,
document.getElementById('root')
);
});
React Router 1.0
React.render(
<Provider store={store}>
{() => <Router history={history}>...</Router>}
</Provider>,
targetEl
);
connect([mapStateToProps], [mapDispatchToProps], [mergeProps])
Connects a React component to a Redux store.
Arguments
-
[mapStateToProps(state): stateProps
] (Function): If specified, the component will subscribe to Redux store updates. Any time it updates, mapStateToProps
will be called. Its result must be a plain object, and it will be merged into the component’s props. If you omit it, the component will not be subscribed to the Redux store.
-
[mapDispatchToProps(dispatch): dispatchProps
] (Object or Function): If an object is passed, each function inside it will be assumed to be a Redux action creator. An object with the same function names, but bound to a Redux store, will be merged into the component’s props. If a function is passed, it will be given dispatch
. It’s up to you to return an object that somehow uses dispatch
to bind action creators in your own way. (Tip: you may use bindActionCreators()
helper from Redux.) If you omit it, the default implementation just injects dispatch
into your component’s props.
-
[mergeProps(stateProps, dispatchProps, parentProps): props
] (Function): If specified, it is passed the result of mapStateToProps()
, mapDispatchToProps()
, and the parent props
. The plain object you return from it will be passed as props to the wrapped component. You may specify this function to select a slice of the state based on props, or to bind action creators to a particular variable from props. If you omit it, { ...parentProps, ...stateProps, ...dispatchProps }
is used by default.
Returns
A React component class that injects state and action creators into your component according to the specified options.
-
It needs to be invoked two times. First time with its arguments described above, and second time, with the component: connect(mapStateToProps, mapDispatchToProps, mergeProps)(MyComponent)
.
-
The mapStateToProps
function takes a single argument of the entire Redux store’s state and returns an object to be passed as props. It is often called a selector. Use reselect to efficiently compose selectors and compute derived data.
-
To use connect()
, the root component of your app must be wrapped into <Provider>{() => ... }</Provider>
before being rendered.
Examples
Inject just dispatch
and don't listen to store
export default connect()(TodoApp);
Inject dispatch
and every field in the global state (SLOW!)
export default connect(state => state)(TodoApp);
Inject dispatch
and todos
function mapStateToProps(state) {
return { todos: state.todos };
}
export default connect(mapStateToProps)(TodoApp);
Inject todos
and all action creators (addTodo
, completeTodo
, ...)
import * as actionCreators from './actionCreators';
function mapStateToProps(state) {
return { todos: state.todos };
}
export default connect(mapStateToProps, actionCreators)(TodoApp);
Inject todos
and all action creators (addTodo
, completeTodo
, ...) as actions
import * as actionCreators from './actionCreators';
import { bindActionCreators } from 'redux';
function mapStateToProps(state) {
return { todos: state.todos };
}
function mapDispatchToProps(dispatch) {
return { actions: bindActionCreators(actionCreators, dispatch) };
}
export default connect(mapStateToProps, mapDispatchToProps)(TodoApp);
Inject todos
and a specific action creator (addTodo
)
import { addTodo } from './actionCreators';
import { bindActionCreators } from 'redux';
function mapStateToProps(state) {
return { todos: state.todos };
}
function mapDispatchToProps(dispatch) {
return bindActionCreators({ addTodo }, dispatch);
}
export default connect(mapStateToProps, mapDispatchToProps)(TodoApp);
Inject todos
, todoActionCreators as todoActions
, and counterActionCreators as counterActions
import * as todoActionCreators from './todoActionCreators';
import * as counterActionCreators from './counterActionCreators';
import { bindActionCreators } from 'redux';
function mapStateToProps(state) {
return { todos: state.todos };
}
function mapDispatchToProps(dispatch) {
return {
todoActions: bindActionCreators(todoActionCreators, dispatch),
counterActions: bindActionCreators(counterActionCreators, dispatch)
};
}
export default connect(mapStateToProps, mapDispatchToProps)(TodoApp);
Inject todos
, and todoActionCreators and counterActionCreators together as actions
import * as todoActionCreators from './todoActionCreators';
import * as counterActionCreators from './counterActionCreators';
import { bindActionCreators } from 'redux';
function mapStateToProps(state) {
return { todos: state.todos };
}
function mapDispatchToProps(dispatch) {
return {
actions: bindActionCreators({ ...todoActionCreators, ...counterActionCreators }, dispatch)
};
}
export default connect(mapStateToProps, mapDispatchToProps)(TodoApp);
Inject todos
, and all todoActionCreators and counterActionCreators directly as props
import * as todoActionCreators from './todoActionCreators';
import * as counterActionCreators from './counterActionCreators';
import { bindActionCreators } from 'redux';
function mapStateToProps(state) {
return { todos: state.todos };
}
function mapDispatchToProps(dispatch) {
return bindActionCreators(Object.assign({}, todoActionCreators, counterActionCreators), dispatch);
}
export default connect(mapStateToProps, mapDispatchToProps)(TodoApp);
Inject todos
of a specific user depending on props, and inject props.userId
into the action
import * as actionCreators from './actionCreators';
function mapStateToProps(state) {
return { todos: state.todos };
}
function mergeProps(stateProps, dispatchProps, parentProps) {
return Object.assign({}, parentProps, {
todos: stateProps.todos[parentProps.userId],
addTodo: (text) => dispatchProps.addTodo(parentProps.userId, text)
});
}
export default connect(mapStateToProps, actionCreators, mergeProps)(TodoApp);
Troubleshooting
Make sure to check out Troubleshooting Redux first.
My views aren’t updating!
See the link above.
In short,
- Reducers should never mutate state, they must return new objects, or React Redux won’t see the updates.
- Make sure you either bind action creators with
mapDispatchToState
argument to connect()
or with bindActionCreators()
method, or that you manually call dispatch()
. Just calling your MyActionCreators.addTodo()
function won’t work because it just returns an action, but not dispatches it.
My views aren’t updating on route change with React Router 0.13
If you’re using React Router 0.13, you might bump into this problem. The solution is simple: whenever you use <RouteHandler>
or the Handler
provided by Router.run
, pass the router state to it.
Root view:
Router.run(routes, Router.HistoryLocation, (Handler, routerState) => {
React.render(
<Provider store={store}>
{() => <Handler routerState={routerState} />} // note "routerState" here
</Provider>,
document.getElementById('root')
);
});
Nested view:
render() {
return <RouteHandler routerState={this.props.routerState} />;
}
Conveniently, this gives your components access to the router state!
You can also upgrade to React Router 1.0 which shouldn’t have this problem. (Let us know if it does!)
I have some weird context error
If you have context issues, make sure you don’t have duplicate React on the page.
Also make sure you didn’t forget to wrap your root component in <Provider>
.
License
MIT