Replies: 1 comment 1 reply
-
As long as the loader doesn't return another error there shouldn't be a reason that the error boundary continues to render. Do you have a repro showing the problem? |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Hello, I have a case where I have a route's
loader
throw an error and theErrorBoundary
is rendered. But after that, if thatloader
is triggered again and return a successful response, theErrorBoundary
will not disappear (so that my route could be rendered instead).I know that trigger the whole web reload works but are there any different alternatives?
Beta Was this translation helpful? Give feedback.
All reactions