From ca0a4a948bfbad58681265a86555ea67c84bf148 Mon Sep 17 00:00:00 2001 From: Toru Kobayashi Date: Thu, 27 Jul 2017 22:57:33 +0900 Subject: [PATCH] Add a link for the error boundaries codemod into the blog post (#10305) * Add a link for the error boundaries codemod into the blog post * Update 2017-07-26-error-handling-in-react-16.md --- docs/_posts/2017-07-26-error-handling-in-react-16.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/_posts/2017-07-26-error-handling-in-react-16.md b/docs/_posts/2017-07-26-error-handling-in-react-16.md index 24cdb58e7f..d739c53bc0 100644 --- a/docs/_posts/2017-07-26-error-handling-in-react-16.md +++ b/docs/_posts/2017-07-26-error-handling-in-react-16.md @@ -98,3 +98,5 @@ Error boundaries preserve the declarative nature of React, and behave as you wou ## Naming Changes from React 15 React 15 included a very limited support for error boundaries under a different method name: `unstable_handleError`. This method no longer works, and you will need to change it to `componentDidCatch` in your code starting from the first 16 beta release. + +For this change, we’ve provided [a codemod](https://github.com/reactjs/react-codemod#error-boundaries) to automatically migrate your code.