From 0741c81a14848dbbd578dcb966bdde7d03b93612 Mon Sep 17 00:00:00 2001 From: Patrick Smith Date: Fri, 21 Feb 2020 04:17:03 +1100 Subject: [PATCH] "async" mode to "concurrent" mode (#2761) Should hooks such as `useLayoutEffect`, `useEffect`, etc also be listed in the "Render phase lifecycles" section? --- content/docs/strict-mode.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/strict-mode.md b/content/docs/strict-mode.md index b7d8b647..46233199 100644 --- a/content/docs/strict-mode.md +++ b/content/docs/strict-mode.md @@ -32,7 +32,7 @@ When strict mode is enabled, React compiles a list of all class components using ![](../images/blog/strict-mode-unsafe-lifecycles-warning.png) -Addressing the issues identified by strict mode _now_ will make it easier for you to take advantage of async rendering in future releases of React. +Addressing the issues identified by strict mode _now_ will make it easier for you to take advantage of concurrent rendering in future releases of React. ### Warning about legacy string ref API usage {#warning-about-legacy-string-ref-api-usage} @@ -83,7 +83,7 @@ Conceptually, React does work in two phases: * The **render** phase determines what changes need to be made to e.g. the DOM. During this phase, React calls `render` and then compares the result to the previous render. * The **commit** phase is when React applies any changes. (In the case of React DOM, this is when React inserts, updates, and removes DOM nodes.) React also calls lifecycles like `componentDidMount` and `componentDidUpdate` during this phase. -The commit phase is usually very fast, but rendering can be slow. For this reason, the upcoming async mode (which is not enabled by default yet) breaks the rendering work into pieces, pausing and resuming the work to avoid blocking the browser. This means that React may invoke render phase lifecycles more than once before committing, or it may invoke them without committing at all (because of an error or a higher priority interruption). +The commit phase is usually very fast, but rendering can be slow. For this reason, the upcoming concurrent mode (which is not enabled by default yet) breaks the rendering work into pieces, pausing and resuming the work to avoid blocking the browser. This means that React may invoke render phase lifecycles more than once before committing, or it may invoke them without committing at all (because of an error or a higher priority interruption). Render phase lifecycles include the following class component methods: * `constructor`