Replies: 1 comment
-
Any update on this? I can make a PR, but wanted to ensure this change was acceptable to the community. I can introduce this behind a new prop like |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My use case seems like it should be the component default and I'm needing to make a wrapper to add this logic.
I have a loader that provides a deferred promise like so
I have a route errorElement defined that is well designed for uncaught exceptions "something went wrong". In the case where
data
fails to load I want to show the AwaiterrorElement
. But in the case where there's a render error in the child components, I do not want the Await errorElement but rather to bubble up to my route error.It seems strange to me the Await acts as a react tree error boundary when it should just monitor the
resolve
status.This is the simple wrapper code I have I'd like to submit to master
Beta Was this translation helpful? Give feedback.
All reactions