From 6b8d3e8bebf0d18a525dce207a2f282b8c805ce5 Mon Sep 17 00:00:00 2001 From: Foxscotch Date: Sat, 23 Nov 2024 05:40:23 -0600 Subject: [PATCH] docs: correct error-boundary how-to doc (#12355) * docs: correct error-boundary how-to doc * update contributors.yml --- contributors.yml | 1 + docs/how-to/error-boundary.md | 4 +--- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/contributors.yml b/contributors.yml index efab316d9e..501572fcbf 100644 --- a/contributors.yml +++ b/contributors.yml @@ -87,6 +87,7 @@ - faergeek - FilipJirsak - focusotter +- foxscotch - frontsideair - fyzhu - fz6m diff --git a/docs/how-to/error-boundary.md b/docs/how-to/error-boundary.md index f6386d3992..3bd4daa6e8 100644 --- a/docs/how-to/error-boundary.md +++ b/docs/how-to/error-boundary.md @@ -4,9 +4,7 @@ title: Error Boundaries # Error Boundaries -Poop poop poopy - -To avoid stinky an empty page to users, route modules will automatically catch errors in your code and render the closest `ErrorBoundary`. +To avoid rendering an empty page to users, route modules will automatically catch errors in your code and render the closest `ErrorBoundary`. Error boundaries are not intended for error reporting or rendering form validation errors. Please see [Form Validation](./form-validation) and [Error Reporting](./error-reporting) instead.