From c3ce14a373a5f76f1d28e06d976baecc4dade8c2 Mon Sep 17 00:00:00 2001 From: Spen Taylor Date: Wed, 11 Jan 2017 01:02:22 +1100 Subject: [PATCH] [Docs] Replace 'mix in' in PureComponent notes (#8730) * [Docs] Replace 'mix in' in PureComponent notes * Style nit --- docs/docs/reference-react.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/reference-react.md b/docs/docs/reference-react.md index bb106890b2..6190bb94c2 100644 --- a/docs/docs/reference-react.md +++ b/docs/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".