Can useMutation be called asynchronously?

[lucasmogari]

When making a lot of requests, I noted that a request is only made, only after the previous on returned.

So if a request is slow to return, the calls to the mutate function are ignored while waiting.

Is this how it's supposed to work?

[tannerlinsley]

So it’s seems less to do with the asynchronous nature and more to do with debouncing. Now that you bring it up there are definitely use cases for firing off multiple mutations in succession. This would mean though that previous promises would be ignored in the status, data and error state tracking.

[lucasmogari]

I was using for a chat app. Every time an user sends a message, it would send a request to save the message. So some messages were ignored. Maybe this is not a good use case for useMutation.

[tannerlinsley]

useMutation is really useful primarily for a few things:

• Simply tracking promise status and data/error
• Declaratively using onSuccess/onError/onSettled to trigger query refetching or direct cache mutations

If you don't need or want either of those, then useMutation may not be useful to you. However, if you are interested in either of those, we could easily add in what I talked about where status, data and error would only be tracked for the latest issued promise. The onWhatever callbacks would still get fired for all issued mutations though.

[lucasmogari]

So I'll use it for another things later.

But for this chat, the useInfiniteQuery is awesome for listing messages/scrolling old messages!

[tannerlinsley]

Cool. Also, FYI, but the latest version allows useMutation to have multiple outgoing requests.

[GeospatialMax]

@tannerlinsley I am running into an issue where I call the mutate function returned by useMutation multiple times and it only ever seems to run the mutation for the very last call. Is this expected behaviour? And is there any way to get around it? Your last post suggests that it should be possible to have mutliple consecutive calls, but how would I achieve this?

Thanks in advance!

[tannerlinsley]

I'll take a looksie.

[tannerlinsley]

You should be able to mutate() as much as you want, but the lifecycle options will only work for the latest call you've made.

[tannerlinsley]

So if you're firing off multiple mutations that overlap, you can't rely on lifecycle callbacks getting called all the time for out-of-date mutations that were already issued.

[kizivat]

Hello, just came across the same issue. I created a sandbox replicating the issue here: https://codesandbox.io/s/awesome-williams-gt0ib?file=/src/App.js

Edit: To describe what's happening that is unexpected: As @GeospatialMax said, patchTodos is only called for the very last call of mutate.

[tannerlinsley]

What version are y’all on?

[kizivat]

What version are y’all on?

The sandbox above uses version 1.5.8

[GeospatialMax]

What version are y’all on?

I am on 1.5.5 at the moment.

[kizivat]

Jus tried it in 2.0.9*, seems to have the same issue

*Edit: 2.0.3 - sorry