chore(react-query): add warning when useSuspenseQuery is used without queryFn #8700
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
… queryFn Added a console warning in development mode when useSuspenseQuery is called without a queryFn or initialData. This helps developers avoid potential issues by ensuring at least one of them is provided.
|
Sorry, I misunderstood the root cause. I’ll submit the PR again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
useSuspenseQueryis designed to accept queryFn as an optional parameter. (related #8176)However, when I built my Next.js app using
useSuspenseQuerywithoutqueryFn, I encountered the following error.Error: Missing queryFn:(This Picture is
@tanstack/query-example-react-nextjs)The reason my Next.js app was able to run without queryFn or initialData was that I had already received the data on the Server-Side using HydrationBoundary.
To prevent this situation, I have added a warning message.
Alternatively, this could be addressed by modifying the implementation like the example below, but I don’t think this would be the best approach: