You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To temporary reply to the questions (which of course can completely be improved, this is rather a first step), in the PR I have just opened (in draft):
for the moment, I am returning the data as an array of objects with a similar structure to the query entries
if the entry doesn't exist, I create it to have reactivity working on it (there is probably a workaround though)
Also, I am wondering if the composable should be called useQueryState (singular) or useQueriesState (plural), since it can handle the aggregation of several queries? Or an alternative could be provide two composables (useQueryState and useQueriesState).
I think returning the aggregation is fine. But I think that useMutationsState() is more important than useQueryState(). In fact, I'm not sure about the usefulness of useQueriesState() without all of the options as it could start in an incoherent state (no initial data). So I think we should probably just add the mutation's one first and leave this for later
Allows retrieving the query state by key
data
,error
, andstatus
? Should each have an individual array, an object, a map?Same questions for
useMutationState()
The text was updated successfully, but these errors were encountered: