Repository navigation
fix: resolve suspense queries when data gets into the cache by other means #10994
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
f581dfc
fix: resolve suspense queries when data gets into the cache by other …
TkDodo 81ff18f
changeset
TkDodo d19a32d
fix: lazy init promise
TkDodo 8f0fb9a
ci: apply automated fixes
autofix-ci[bot] 86ff705
port to preact
TkDodo 5a61227
Apply suggestion from @TkDodo
TkDodo 46bed97
Merge branch 'main' into feature/suspense-resolving-data
TkDodo 2f17723
fix: Recreate the thenable on query-hash switches.
TkDodo c7773be
fix streaming
TkDodo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
Recreate the thenable on query-hash switches.
When
packages/query-core/src/queryObserver.tspassesfalsehere for a query change, the'pending'branch reuses the previous query's pending thenable. If the new query is already settled from cache,nextResult.promisestays pending and Suspense can hang indefinitely.Suggested fix
switch (thenable.status) { case 'pending': - if (finalizePending) { - finalizeThenableIfPossible(thenable) - } - return thenable + if (!finalizePending) { + return recreateThenable() + } + finalizeThenableIfPossible(thenable) + return thenable case 'fulfilled': if (isErrorWithoutData || result.data !== thenable.value) { return recreateThenable() }📝 Committable suggestion
🤖 Prompt for AI Agents