From da29d893e49ab33bfda84036754c9128401cbf97 Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Tue, 6 Feb 2018 10:48:38 -0800 Subject: [PATCH] Added note about string ref API to strict mode section --- content/blog/2018-02-07-react-v-16-3.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/blog/2018-02-07-react-v-16-3.md b/content/blog/2018-02-07-react-v-16-3.md index b80838c3..6f526b62 100644 --- a/content/blog/2018-02-07-react-v-16-3.md +++ b/content/blog/2018-02-07-react-v-16-3.md @@ -57,6 +57,11 @@ We are also adding a new static lifecycle, `getDerivedStateFromProps`, as a safe Although it is not possible for strict mode to catch all problems (e.g. certain types of mutation), it can help with many. If you see warnings in strict mode, those things will likely cause bugs for async rendering. -In version 16.3, `StrictMode` helps with two things: identifying unsafe lifecycles and detecting unexpected side effects. Additional functionality will be added with future releases of React. +In version 16.3, `StrictMode` helps with only a handful of things: +* Identifying components with unsafe lifecycles +* Identifying usage of the legacy string ref API +* Detecting unexpected side effects + +Additional functionality will be added with future releases of React. [Learn more about the `StrictMode` component here.](#)