-
-
Notifications
You must be signed in to change notification settings - Fork 10.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: useRevalidator doesn't clear route errors #9713
Comments
Yeah this feels like a bug. The error boundary resets on location changes (since there was no |
This issue has been automatically marked stale because we haven't received a response from the original author in a while 🙈. This automation helps keep the issue tracker clean from issues that are not actionable. Please reach out if you have more information for us or you think this issue shouldn't be closed! 🙂 If you don't do so within 7 days, this issue will be automatically closed. |
Bump |
This is fixed by #10369 and will be available once React Router 6.11.0 is release |
That's great news - thanks |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
What version of React Router are you using?
6.4
Steps to Reproduce
Throw an error to show the error element. In the error element, resolve the problem and call revalidation.revalidate(). The loader reloads, throws no errors, and then renders the error element
https://stackblitz.com/edit/github-gkokwd?file=src%2FApp.tsx
Expected Behavior
Once the error has been resolved by the error component, revalidating should cause the normal component to be rendered
Actual Behavior
The revalidation is called, the loader is run and returns without error, but the error component is shown
The text was updated successfully, but these errors were encountered: