chore(react-query): add warning when useBaseQuery is called without a queryFn #8701
+6
−0
Conversation
This file contains 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 error in development mode when useBaseQuery is called without a queryFn or default queryFn. This helps developers avoid potential issues by ensuring at least one of them is provided.
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.
Added a console error in development mode when
useBaseQueryis called without aqueryFnordefault queryFn.This helps developers avoid potential issues by ensuring at least one of them is provided.
If you prefer, I can change it to
throw Errorinstead of a console error. Let me know if needed.Commit Result
(This Picture is
@tanstack/query-example-react-nextjs)Issue Situation
I was able to run my Next.js app without
queryFnwithout any issues in Dev. However, when I built my Next.js app usinguseSuspenseQuerywithout queryFn, 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
queryFnor default queryFn was that I had already received the data on the Server-Side usingHydrationBoundary( => initial data).To prevent this situation, I have added a warning message.