-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Add onSuccess/onError/onSettled callbacks to useQuery #9943
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 all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8a41e99
- useQuery onSuccess onError onSettle
Phenek d323e55
- useQuery callbacks core tests
Phenek e6d6729
- tests callbacks , and
Phenek e863bf0
- tests callbacks `onSuccess`, `onError` and `onSettled`
Phenek 7704d32
- review
Phenek 949a12c
- documentation react & solid
Phenek 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
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.
Lifecycle callbacks should be based on observer result, not raw
query.stateRight now
#notifydecides which callbacks to fire and which arguments to pass by inspectingnotifyOptions.query.state.status/data/error. This diverges from the observer’s computed result in several important cases:select(and select errors):createResultcan setstatus = 'error'anderror = this.#selectErrorsolely at the observer level.query.state.statusandquery.state.errorremain whatever the fetch layer set ('success'/null).onError/erroronSettledwill never see select errors; instead, the success branch may fire with stale data.placeholderData:createResultmarksstatus = 'success'andisPlaceholderData = true, butquery.state.statuscan still be'pending'.Refetching after success/error:
query.state.statusstays'success'while onlyfetchStatustoggles.onSuccess/onSettledwill fire both when refetch starts (no new data) and again when it completes, which is likely more often than intended.Because
updateResultalready computesnextResultand assignsthis.#currentResultimmediately before calling#notify, you can avoid these inconsistencies by basing the callbacks onthis.#currentResult(ornextResult) instead:this.#currentResult.statusto choose between success/error branches.this.#currentResult.dataandthis.#currentResult.errorintoonSuccess/onError/onSettled.dataUpdatedAtchange) to avoid duplicate callbacks when only fetchStatus flips.This would align the lifecycle hooks with what hook consumers actually see in
UseQueryResult, and ensure select/placeholder behaviors are reflected correctly.Also applies to: 731-752
🤖 Prompt for AI Agents