Paul O’Shannessy
11 years ago
3 changed files with 33 additions and 0 deletions
@ -0,0 +1,30 @@ |
|||
--- |
|||
id: pure-render-mixin |
|||
title: PureRenderMixin |
|||
layout: docs |
|||
permalink: pure-render-mixin.html |
|||
prev: update.html |
|||
--- |
|||
|
|||
If your React component's render function is "pure" (in other words, it renders the same result given the same props and state), you can use this mixin for a considerable performance boost. |
|||
|
|||
Example: |
|||
|
|||
```js |
|||
var PureRenderMixin = require('react').addons.PureRenderMixin; |
|||
React.createClass({ |
|||
mixins: [PureRenderMixin], |
|||
|
|||
render: function() { |
|||
return <div className={this.props.className}>foo</div>; |
|||
} |
|||
}); |
|||
``` |
|||
|
|||
Under the hood, the mixin implements [shouldComponentUpdate](/react/docs/component-specs.html#updating-shouldcomponentupdate), in which it compares the current props and state with the next ones and returns `false` if the equalities pass. |
|||
|
|||
> Note: |
|||
> |
|||
> 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. |
|||
> |
|||
> Furthermore, `shouldComponentUpdate` skips updates for the whole component subtree. Make sure all the children components are also "pure". |
Loading…
Reference in new issue