From ee1f4167908d42c6a67a51b63ba683789d57c0cf Mon Sep 17 00:00:00 2001 From: Szymon Nowicki Date: Fri, 15 Dec 2017 17:29:55 +0100 Subject: [PATCH] Update `React.PureComponent` reference. Maybe I'm somehow weird, but I lived for some time with an idea that `React.Component` does implement `shouldComponentUpdate` with deep comparison. `React.PureComponent` is faster because it compares shallowly. The changes I propose should avoid this "implicit" kind of way of thinking, since it would explicitly state that `React.Component` does not compare anything. --- content/docs/reference-react.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/reference-react.md b/content/docs/reference-react.md index 968d376c..05b81e01 100644 --- a/content/docs/reference-react.md +++ b/content/docs/reference-react.md @@ -71,9 +71,9 @@ See the [React.Component API Reference](/docs/react-component.html) for a list o ### `React.PureComponent` -`React.PureComponent` is exactly like [`React.Component`](#reactcomponent), but implements [`shouldComponentUpdate()`](/docs/react-component.html#shouldcomponentupdate) with a shallow prop and state comparison. +`React.PureComponent` is exactly like [`React.Component`](#reactcomponent), but implements [`shouldComponentUpdate()`](/docs/react-component.html#shouldcomponentupdate) with a shallow prop and state comparison, which [`React.Component`](#reactcomponent) is missing completely. -If your React component's `render()` function renders the same result given the same props and state, you can use `React.PureComponent` for a performance boost in some cases. +If your React component's `render()` function renders the same result given the same props and state, you can use `React.PureComponent` for a performance boost in some cases. > Note >