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
The useSyncDataMutation is executed in a button handler and in 3.13.0 and previous versions, the onCompleted from useQueryJustChangelistQuery was executed with the new data. Starting from 3.13.1 I see the request to the server being made but the handler is not being executed.
Note: I'll try to create a codesandbox and I'll update this description
Link to Reproduction
WIP
Reproduction Steps
No response
@apollo/client version
3.13.1
The text was updated successfully, but these errors were encountered:
A reproduction would be great. The only change I see 3.13.1 that could possibly be related is #12369 which uses a network-only fetch policy for refetches if the fetch policy is cache-and-network (previously it would refetch with a cache-and-network fetch policy).
This shouldn't affect anything in regards to onCompleted though so this is a bit odd. By chance, do you see the same issue if you switch your fetch policy to network-only in 3.13.0 and/or 3.13.1?
Hey @jerelmiller ! Thanks for your quick response!
I tested several values for the fetch policy, including network-only and it didn't worked.
Regarding the reproduction I'm still working on it I'll update the original message and add a new comment with it once I finish it
Issue Description
In our component we have the following mutation with a refetch option set for a previously executed query.
The
useSyncDataMutation
is executed in a button handler and in3.13.0
and previous versions, theonCompleted
fromuseQueryJustChangelistQuery
was executed with the new data. Starting from3.13.1
I see the request to the server being made but the handler is not being executed.Note: I'll try to create a codesandbox and I'll update this description
Link to Reproduction
WIP
Reproduction Steps
No response
@apollo/client
version3.13.1
The text was updated successfully, but these errors were encountered: