How can I refetch in the background when invalidating a query?

Original message was deleted

.invalidate().invalidate() should do that

if you don't

await

await

it in an onSuccess()onSuccess() of the mutation it won't delay the "loading state"

Alex / KATT 🐱•2/6/23, 6:13 PM

then you're using it wrong

Alex / KATT 🐱•2/6/23, 6:13 PM

https://tanstack.com/query/v4/docs/react/guides/query-invalidation

Query Invalidation | TanStack Query Docs

Waiting for queries to become stale before they are fetched again doesn't always work, especially when you know for a fact that a query's data is out of date because of something the user has done. For that purpose, the QueryClient has an invalidateQueries method that lets you intelligently mark queries as stale and potentially refetch them too!

Alex / KATT 🐱•2/6/23, 6:13 PM

https://tanstack.com/query/v4/docs/react/guides/invalidations-from-mutations

Invalidations from Mutations | TanStack Query Docs

Invalidating queries is only half the battle. Knowing when to invalidate them is the other half. Usually when a mutation in your app succeeds, it's VERY likely that there are related queries in your application that need to be invalidated and possibly refetched to account for the new changes from your mutation.

For example, assume we have a mu...

Alex / KATT 🐱•2/8/23, 11:29 AM

that should invalidate in the background

Ruslan Gonzalez•10/18/23, 10:35 AM

So, question, just imagine I have two types of logic around my codebase. One is a query from the SSR and the other a Mutation from the client side (as often) how do I revalidate SSR on client's mutations?