Query callbacks and mutation direct payload

[NicolaSpadari]

I'm using pinia colada to structure a very large and complex codebase with ~100 vuex store modules (refactoring an old vuex vue 2 app to nuxt 4)
Pinia Colada seems the best option to structure the codebase and reuse fetch actions instead of a plain pinia store.

• Almost all api calls require authentication, handle server side with nuxt auth utils. if the token/refresh token expires, i need to intercept the error 401, for example when fetching user data from the api, and redirect/logout. onSuccess and onError callbacks for queries would be very useful in this situation but looks like it's not available for queries, only for mutations, is that right? Can this feature be implemented or what's the best way to handle a case like this?
• Reusable mutations are also a nice feature, as per docs Nuxt can define the payload inside the reusable mutation with useState, and edit it before fetching/refetching the mutation. I find this a bit cumbersome. it would be really cool to just call fetch or refetch passing an object of options as payload directly to the function. As my understanding this is also not currently possible, am I correct?
• If my query has a parameters object to be passed as query params to the fetch, let's say for example current page: number, searchterm: string, everytime i digit something v-model binded to the searchterm causes the query to execute. what's the best way to debounce the input? A solution I found is using @update:modelValue="myDebouncedFn" instead of using v-model, but that required defining this debounced function almost everywhere and it's not very scalable. Maybe is there a way to handle the delay or debounce inside the query itself somehow?

[posva]

• see Add a hooks system to useQuery #309
• you can define arbitrary parameters in mutation so that should just work
• you can debounce at the network layer (in your fetch abstraction), debounce the fetch call (easiest), or create a plugin that adds a debounce option