Bug - use query is repeatly called when init component
See original GitHub issueI’ve attached here the bug I am using
"@apollo/client": "^3.0.0-beta.50"


Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
useQuery | TanStack Query Docs
The function that the query will use to request data. Receives a QueryFunctionContext; Must return a promise that will either resolve data or...
Read more >UseEffect being called multiple times - Stack Overflow
Your useEffect is executed only once per render cycle, but you have several state updates in your useEffect which cause a re-render.
Read more >What I learned from React-Query, and why I won't use it again
We think that such a process should not be managed within the component. It affects the entire app, even beyond (the Iframe), and...
Read more >Fetching data with queries | Full-Stack Quickstart
This component passes our GET_LAUNCHES query to useQuery and obtains data , loading , and error properties from the result. Depending on the...
Read more >Using Suspense and React Query: Tutorial with examples
React Suspense simplifies managing loading states in React components, supporting fallbacks in case the component hasn't finished loading ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
the issue is when you setup
the version . “@apollo/client”: “^3.0.0-beta.50” doesn’t trigger onCompleted function anymore…
ANY Idea was is BROKEN?
is breaking all my project can Apollo CLIENT TEAM FIX THOSE ISSUES ?
I am also running into this, using 3.0.0-beta.53. It happens immediately when using
useQuery
, but also happens once the query function has been called when usinguseLazyQuery
. I’ve gone back to 3.0.0-beta.45 for now which doesn’t seem to have the issue.