Skip to content

Commit

Permalink
Merge pull request #511 from reactjs/sync-a30e1f95
Browse files Browse the repository at this point in the history
Sync with react.dev @ a30e1f9
  • Loading branch information
AhmedBaset authored Jul 17, 2023
2 parents 49b0a70 + 1245064 commit ac4cb6f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/content/reference/react/Component.md
Original file line number Diff line number Diff line change
Expand Up @@ -1393,7 +1393,7 @@ Then you can wrap a part of your component tree with it:
If `Profile` or its child component throws an error, `ErrorBoundary` will "catch" that error, display a fallback UI with the error message you've provided, and send a production error report to your error reporting service.
You don't need to wrap every component into a separate error boundary. When you think about the [granularity of error boundaries,](https://aweary.dev/fault-tolerance-react/) consider where it makes sense to display an error message. For example, in a messaging app, it makes sense to place an error boundary around the list of conversations. It also makes sense to place one around every individual message. However, it wouldn't make sense to place a boundary around every avatar.
You don't need to wrap every component into a separate error boundary. When you think about the [granularity of error boundaries,](https://www.brandondail.com/posts/fault-tolerance-react) consider where it makes sense to display an error message. For example, in a messaging app, it makes sense to place an error boundary around the list of conversations. It also makes sense to place one around every individual message. However, it wouldn't make sense to place a boundary around every avatar.
<Note>
Expand Down

0 comments on commit ac4cb6f

Please sign in to comment.