Browse Source

[Docs] Replace 'mix in' in PureComponent notes (#8730)

* [Docs] Replace 'mix in' in PureComponent notes

* Style nit
main
Spen Taylor 8 years ago
committed by Dan Abramov
parent
commit
201cce9207
  1. 2
      docs/reference-react.md

2
docs/reference-react.md

@ -106,7 +106,7 @@ If your React component's `render()` function renders the same result given the
> Note
> `React.PureComponent`'s `shouldComponentUpdate()` 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()`](/react/docs/react-component.html#forceupdate) when you know deep data structures have changed. Or, consider using [immutable objects](https://facebook.github.io/immutable-js/) to facilitate fast comparisons of nested data.
> `React.PureComponent`'s `shouldComponentUpdate()` only shallowly compares the objects. If these contain complex data structures, it may produce false-negatives for deeper differences. Only extend `PureComponent` when you expect to have simple props and state, or use [`forceUpdate()`](/react/docs/react-component.html#forceupdate) when you know deep data structures have changed. Or, consider using [immutable objects](https://facebook.github.io/immutable-js/) to facilitate fast comparisons of nested data.
>
> Furthermore, `React.PureComponent`'s `shouldComponentUpdate()` skips prop updates for the whole component subtree. Make sure all the children components are also "pure".

Loading…
Cancel
Save