The value of mutation abstraction

[ylc395]

I'm new to this library and thanks very much for everyone's great work. But I got a question: What's the value of mutation abstraction?

Query abstraction enjoys benefits of global caching / auto re-fetch / etc. provided by this library, but they're all not suitable for mutation. So there is no much difference between using mutation abstraction and invoking POST/DELETE/ etc. request directly, is it right? Can we say that: let's say the value of Query abstraction is 10, the value of mutation abstraction is maybe 3? Or, am I missing something about mutation?

Disclaimer: Not for debating, just for a better understanding of this library.

[TkDodo]

• it tracks loading and error states for you
• it lets you build optimistic updates
• you can read values of mutations in other components with useMutationState

you have to decide for yourself if that’s “worth it” or not.

[ylc395]

After reading some of your blogs, I can find some extra case:

• set some global mutation callback to do something, such as invalidateQueries, especially by invoking it by meta option
• ...