From 1602db79a7ba1e586ec618de72ef8c0cd905a214 Mon Sep 17 00:00:00 2001 From: Dan Abramov Date: Thu, 27 Jul 2017 10:48:37 +0100 Subject: [PATCH] Reword further --- _posts/2017-07-26-error-handling-in-react-16.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2017-07-26-error-handling-in-react-16.md b/_posts/2017-07-26-error-handling-in-react-16.md index 739eba36..24cdb58e 100644 --- a/_posts/2017-07-26-error-handling-in-react-16.md +++ b/_posts/2017-07-26-error-handling-in-react-16.md @@ -15,7 +15,7 @@ In the past, JavaScript errors inside components used to corrupt React’s inter A JavaScript error in a part of the UI shouldn’t break the whole app. To solve this problem for React users, React 16 introduces a new concept of an “error boundary”. -Error boundaries are React components that **catch JavaScript errors in their descendants, log those errors, and display a fallback UI** instead of the component tree that crashed. Error boundaries catch errors during rendering, in lifecycle methods, and in constructors of the whole tree below them. +Error boundaries are React components that **catch JavaScript errors anywhere in their child component tree, log those errors, and display a fallback UI** instead of the component tree that crashed. Error boundaries catch errors during rendering, in lifecycle methods, and in constructors of the whole tree below them. A class component becomes an error boundary if it defines a new lifecycle method called `componentDidCatch(error, info)`: