{"componentChunkName":"component---src-templates-docs-js","path":"/docs/pure-render-mixin.html","result":{"data":{"markdownRemark":{"html":"
\n

Note:

\n

PureRenderMixin is a legacy add-on. Use React.PureComponent instead.

\n
\n

Importing

\n
import PureRenderMixin from 'react-addons-pure-render-mixin'; // ES6\nvar PureRenderMixin = require('react-addons-pure-render-mixin'); // ES5 with npm
\n

Overview

\n

If your React component’s render function renders the same result given the same props and state, you can use this mixin for a performance boost in some cases.

\n

Example:

\n
const createReactClass = require('create-react-class');\n\ncreateReactClass({\n  mixins: [PureRenderMixin],\n\n  render: function() {\n    return <div className={this.props.className}>foo</div>;\n  }\n});
\n

Under the hood, the mixin implements shouldComponentUpdate, in which it compares the current props and state with the next ones and returns false if the equalities pass.

\n
\n

Note:

\n

This only shallowly compares the objects. If these contain complex data structures, it may produce false-negatives for deeper differences. Only mix into components which have simple props and state, or use forceUpdate() when you know deep data structures have changed. Or, consider using immutable objects to facilitate fast comparisons of nested data.

\n

Furthermore, shouldComponentUpdate skips updates for the whole component subtree. Make sure all the children components are also “pure”.

\n
","frontmatter":{"title":"PureRenderMixin","next":null,"prev":null},"fields":{"path":"content/docs/addons-pure-render-mixin.md","slug":"docs/pure-render-mixin.html"}}},"pageContext":{"slug":"docs/pure-render-mixin.html"}},"staticQueryHashes":[]}