add isPending to UseMutationReturn

[shrpne]

isPending alias is available in UseQueryReturn but not in UseMutationReturn

[posva]

This is intentional because mutations are not automatically triggered like queries are. In the end isPending() really is just state.value.status === 'pending'

What is the use case? Or is it just really convenience?

[shrpne]

As i understand queries can be configured to not be triggered automatically too, so i don't see any differences with mutations here

Use case is to have a little more convenient alias

I found it strange, that useQuery have this alias and useMutation doesn't have one

[posva]

Yes, they can be configured like that but mutations can't be configured to always trigger initially (or rather it wouldn't make sense).

I will keep this as an idea, it should be doable as a plugin if you really want it. I personally think isLoading is all you need in mutations for 99% of scenarios

[shrpne]

Sorry, I don't understand, checking mutation status.value === 'pending' is pretty normal use case for me, so it's unclear why mutations do not have an alias, like queries do.

In my opinion, queries and mutation APIs should be as similar as possible.

[shrpne]

@posva As another argument: Tanstack query has isPending in useMutation return: https://tanstack.com/query/latest/docs/framework/vue/reference/useMutation

[posva]

That is not an argument, tanstack has a bloated API and is super heavy. If checking the pending status is pretty normal use case for you and you want a boolean, you can create a plugin that adds it, check the plugins/delay. I think this to an agent will yield a functional plugin in a bunch of minutes if you give it the plugin as an example

[shrpne]

• I understand, that 100% match to tanstack is not a goal
• This is too small change to write a plugin, i would prefer using idiomatic pinia-colada way for better interoperability between projects.

But.., my last attempt to advocate for this alias :D

Why i think checking status.value === 'pending' is a normal use case: i understand we are calling mutation manually, but we still need to check in the other parts of code, if it was already called manually or not yet. Manual or automatic way of execution is not affecting the need of checking the status

Even if checking the status of a useMutation is more rare than checking the status of a useQuery - consistency of their APIs is still valuable. Because the concept of having or not having an alias depending on a rarity of the usage may be not clear for the users of Pinia Colada (how it was for me). And the absence of an alias may look like a bug (how it was for me) and may lead to a time-consuming investigation of the reason of the absence of the alias.

So i still believe having few-line alias will not cause bloating and will be very valuable in regards of consistency between useQuery and useMutation APIs (and even between tanstack's useMutation)

[posva]

I checked https://tanstack.com/query/latest/docs/framework/react/reference/useMutation and understand what you use it. So in Pinia Colada mutations have status and asyncStatus and isPending is actually isLoading and isIdle (in TQ) is status.value === 'pending'. Confusing if you come from TQ but I think this version makes much more sense

[posva]

Follow in #457