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
Describe the bug docs state this: onDone(handler): Event hook called when the mutation successfully completes.
But in some cases the onDone is called too early and the globalTracking of mutations fails (does not get reduced to 0).
For example, when the component, who triggered the mutation, gets refetched by onDone, then useGlobalMutationLoading and useMutationLoading would be still in loading state and will never recover. App keeps "loading" even when the requests clearly ended in the network tab of the browser.
Several issues with this behaviour have been reported:
Describe the bug
docs state this:
onDone(handler): Event hook called when the mutation successfully completes.
But in some cases the onDone is called too early and the globalTracking of mutations fails (does not get reduced to 0).
For example, when the component, who triggered the mutation, gets refetched by onDone, then
useGlobalMutationLoading
anduseMutationLoading
would be still in loading state and will never recover. App keeps "loading" even when the requests clearly ended in the network tab of the browser.Several issues with this behaviour have been reported:
useMutationLoading
returnstrue
inonDone
hook #1387To Reproduce
Steps to reproduce the behavior:
Expected behavior
useGlobalMutationLoading()
anduseMutationLoading()
should be already 0 when onDone gets called.Versions
vue: 3.4.27
vue-apollo: 3.1.2
@apollo/client: 3.10.4
The text was updated successfully, but these errors were encountered: