Skip to content

Make error boundary doc more in style with the post #213

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.

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
merged 3 commits into from
Oct 27, 2017
Merged

Conversation

gaearon
Copy link
Member

@gaearon gaearon commented Oct 26, 2017

I find the clarifications different in style from the original post. Tried to make them look more in line with it.

@@ -136,37 +137,42 @@ However, React components are declarative and specify *what* should be rendered:

Error boundaries preserve the declarative nature of React, and behave as you would expect. For example, even if an error occurs in a `componentDidUpdate` hook caused by a `setState` somewhere deep in the tree, it will still correctly propagate to the closest error boundary.

However, an event handler inside of a React component could leverage `try` / `catch` to deal with errors that occur during event handling.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounded a bit like an ad for try/catch :-)

@reactjs-bot
Copy link

Deploy preview ready!

Built with commit 09dbffb

https://deploy-preview-213--reactjs.netlify.com

@reactjs-bot
Copy link

Deploy preview ready!

Built with commit 0589024

https://deploy-preview-213--reactjs.netlify.com

@reactjs-bot
Copy link

Deploy preview ready!

Built with commit e4c9d19

https://deploy-preview-213--reactjs.netlify.com

@gaearon gaearon merged commit ff8ef81 into master Oct 27, 2017
@gaearon
Copy link
Member Author

gaearon commented Oct 27, 2017

I’ll just get it in. I think it’s better this way.

@gaearon gaearon deleted the gaearon-patch-5 branch October 27, 2017 11:51
jhonmike pushed a commit to jhonmike/reactjs.org that referenced this pull request Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants