mutation callback called twice #1604
-
|
the callback inside useMutation seems to be called twice, once before the request has finished (or before sent, i am not sure because the state.isLoading is false for both calls) then the second time once the request is finished: is this an intended behavior? If so, how do I prevent the double invocation? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
it seems |
Beta Was this translation helpful? Give feedback.
-
|
The first callback is designed for GQty to collect the mutation contents, please only do query inputs and field selections there. GQty may call it multiple times for each fetch, because of how React rendering works. (
Everything thrown from your query fetcher is considered a server error, so you may further customize how it behaves there. |
Beta Was this translation helpful? Give feedback.
-
|
I think this expectation needs to be documented, the examples in the docs imply that you can do operations here but in reality this is the return selection |
Beta Was this translation helpful? Give feedback.
-
|
Definitely worth considering, I'll add that to my plans. |
Beta Was this translation helpful? Give feedback.
-
|
@vicary how does the query selector handle if statements? for ex: |
Beta Was this translation helpful? Give feedback.
-
|
It depends on where Technically you can write this statement inside the query selector, but if the fetch result may change the boolean in the chain of effects, you may get infinite fetches. The best solution is to always fetch both fields, but only return one of them from the query selector. |
Beta Was this translation helpful? Give feedback.
The first callback is designed for GQty to collect the mutation contents, please only do query inputs and field selections there. GQty may call it multiple times for each fetch, because of how React rendering works. (
isLoadingis one of the factors to consider)onCompletecallback.onErrorcallback.Everything thrown from your query fetcher is considered a server error, so you may further customize how it behaves there.