docs: add Learn guide for error handling and loader error propagation#152
docs: add Learn guide for error handling and loader error propagation#152
Conversation
Co-authored-by: uhyo <748348+uhyo@users.noreply.github.com>
| <code>entryId</code> comes from the Navigation API’s current | ||
| history entry. It changes when the router moves to a different entry, | ||
| so using it in <code>resetKeys</code> lets the boundary recover when | ||
| the user clicks another link, goes back/forward, or triggers a reload. |
There was a problem hiding this comment.
Statement on reload is inaccurate. Reload doesn't change entry ID.
There was a problem hiding this comment.
Updated in 2430d28. I removed the reload wording and now describe entryId only in terms of moving to a different history entry. Screenshot: /tmp/playwright-logs/learn-error-handling-page-review-fixes.png.
| <strong>Synchronous loader throws</strong> — the router catches | ||
| the error while preparing the matched route and re-throws it during | ||
| that route’s render. The nearest Error Boundary above the route | ||
| catches it. |
There was a problem hiding this comment.
This could be written more from user perspective. Caching is implementation detail.
Let's say that sync loader errors are thrown from that route's Outlet.
There was a problem hiding this comment.
Updated in 2430d28. I rewrote the sync loader bullet to describe the error as being thrown from that route’s <Outlet /> when React renders it. Screenshot: /tmp/playwright-logs/learn-error-handling-page-review-fixes.png.
Co-authored-by: uhyo <748348+uhyo@users.noreply.github.com>
|
@copilot please fix CI failure. |
Co-authored-by: uhyo <748348+uhyo@users.noreply.github.com>
Fixed in 14b3fcb. I checked the failing CI run and it was failing only at |
📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.