status vs asyncStatus

[segevfiner]

Pinia Colada has both status and asyncStatus on queries and I'm not sure when to use which one, and what's the intended idiomatic way to code the template around them to display loading and error states correctly. I couldn't find any clarification in the docs about this, it would be nice to also add an explanation on their differences to the docs.

[posva]

How to use them depends on what you want. The difference is explained in docs, status is for the status of the data asyncStatus for the async status of the query/mutation

[segevfiner]

Can you point where in the docs? I swear I couldn't find it... I assume this has to do with the behavior on refetching where you might have different combinations than just success/idle?

[posva]

https://pinia-colada.esm.dev/quick-start.html#Querying

[segevfiner]

Thanks for pointing it out, but it's not entirely clear there IMHO...

You can infer from that that you might have a success/loading status/asyncStatus respectively on refetching, but it might not be so obvious to everyone, especially on a cursory glance of the docs where someone is just looking for a quick start, and its not obvious if you should prefer checking status, or asyncStatus, or both, in your component and what differences it would make without having to try and reason about it by yourself and playing around with the library.

I believe more detailed docs on the lifecycle of Pinia Colada, including status, asyncStatus, query deduplication, cache expiry and so on could help. Not everyone is intimately familiar with @tanstack/query and just infer that Pinia Colada behaves like it...

[posva]

I created #359
Feel free to leave some feedback