fix: queries should not end up in an error state when a component unmounts #1781
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/tannerlinsley/react-query/9tph6f878 |
boschni
force-pushed
the
feature/no-cancel-error-on-unmount
branch
from
a1bbd40 to
4601704
Compare
Contributor
|
I'm having a persistent bug in an application I'm currently working on due to this bug. I've tested this PR in my codebase and it fixes the bug. Would love to see it released. |
boschni
force-pushed
the
feature/no-cancel-error-on-unmount
branch
from
4601704 to
c9873a9
Compare
Member
|
🎉 This PR is included in version 3.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Any chance this can be shipped in a v2 patch? I'd be happy to put up a PR based off v2.26.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up on: #1412