You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when after first useLazyQuery execution, it re-execute automatically when changes variables. it acts like a useQuery.
In docs, executing queries in response to events besides component rendering. is it correct execution? if so docs should be updated.
When only we clicked clickB Button it calls lazyFetch. (clickC is just useState hooks) but, when we clicked clickB and clickC in order, it called lazyQuery twice.
@rbals0445 this is how useLazyQuery was designed. See this comment for more details. We'll get this updated in the docs (which is being tracked in that issue).
Intended outcome:
when after first useLazyQuery execution, it re-execute automatically when changes variables. it acts like a useQuery.
In docs,
executing queries in response to events besides component rendering.
is it correct execution? if so docs should be updated.When
only
we clickedclickB Button
it calls lazyFetch. (clickC is just useState hooks) but, when we clickedclickB
andclickC
in order, it called lazyQuery twice.Actual outcome:
You can check the result imgs below.
How to reproduce the issue:
-> ClickC does not call lazyFetch(), but automatically call lazyQuery and called onCompleted callback.
-> when clickC there is no call lazyFetch, and when clickB it calls lazyFetch.
Versions
plz clarify this situation and if it is error, change the docs plz. it wastes my time....
The text was updated successfully, but these errors were encountered: