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
client.mutate's update option/callback is intended to be used only when you want to interact with the data store (cache). The update callback itself gets sent a proxy to access the data store, as well as the result of the mutation. When you're using no-cache you shouldn't be interacting with the data store at all. If you want to fire actions after the mutation has completed, use the Promise returned from the client.mutate call.
I am marking this as a bug though, since the docs really aren't very clear about this. I'll get them updated. Thanks!
Intended outcome:
update
option should be called when executingclient.mutate({ ... })
Actual outcome:
update
is not called when executingclient.mutate({ fetchPolicy: 'no-cache' })
How to reproduce the issue:
https://codesandbox.io/s/o98ylor0m5
Version
The text was updated successfully, but these errors were encountered: