Skip to content

Explain how StrictMode affects function components and hooks #2515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gaearon merged 6 commits into from
Mar 30, 2020
Merged

Explain how StrictMode affects function components and hooks #2515

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c4521ef
Update strict-mode.md
eps1lon Oct 29, 2019
d777c53
Fix links
eps1lon Oct 29, 2019
6818ecf
Merge branch 'master' into patch-1
eps1lon Mar 29, 2020
89d1555
docs: specify which kind of function component
eps1lon Mar 29, 2020
f1ac705
Update content/docs/strict-mode.md
eps1lon Mar 29, 2020
b4b1e99
Update strict-mode.md
gaearon Mar 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions content/docs/strict-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,13 +97,13 @@ Render phase lifecycles include the following class component methods:

Because the above methods might be called more than once, it's important that they do not contain side-effects. Ignoring this rule can lead to a variety of problems, including memory leaks and invalid application state. Unfortunately, it can be difficult to detect these problems as they can often be [non-deterministic](https://en.wikipedia.org/wiki/Deterministic_algorithm).

Strict mode can't automatically detect side effects for you, but it can help you spot them by making them a little more deterministic. This is done by intentionally double-invoking the following methods:
Strict mode can't automatically detect side effects for you, but it can help you spot them by making them a little more deterministic. This is done by intentionally double-invoking the following functions:

* Class component `constructor` method
* The `render` method
* `setState` updater functions (the first argument)
* The static `getDerivedStateFromProps` lifecycle
* The `shouldComponentUpdate` method
* Class component `constructor`, `render`, and `shouldComponent` methods
* Class component static `getDerivedStateFromProps` method
* Function component bodies
* State updater functions (the first argument to `setState`)
* Functions passed to `useState`, `useMemo`, or `useReducer`

> Note:
>
Expand Down