react-query-questions
solid-query-questions
table-questions
virtual-questions
router-questions
react-charts-questions
ranger-questions
vue-query-questions
svelte-query-questions
bling-questions
form-questions
angular-query-questions
start-questions
db-questions
start-showcase
router-showcase
📣-announcements
useMutation in Context+Provider infinite calls
createContext and provider to then be able to access it a bit deeper down easily, that'd be useful. I am completely unable to get this to work or understand why I am getting infinite re-renders. I have tried everything chat gippity is suggesting and have googled as much as possible....useMutation refreshing problem
Is select callback only meant for data transformation?
What causes `queryClient.invalidateQueries()` to error when all requests are good?
Is it possible to wait for a few seconds before invalidates the cache in onSuccess?
Can `useQuery`'s result type figure out that all errors throw?
throwOnError is set, one only needs to eliminate pending in order to guarantee this state of affairs. Is this a deliberate design decision, am I doing things wrongly, or is it some sort of inherent TypeScript limitation?TypeError: Cannot read properties of undefined (reading 'fetchStatus')
Quick question about key equality and using it with gql
As long as the query key is serializable using JSON.stringifyDoes this mean they are checked via the JSON serialised version for equality? So if I did:...
with nextjs what is the best way to architect your queries?
SSE background Fetching while component unmount
Weird type bug when using `queryOptions` with `useQueries`
name, the types of results in the combine function seems to be wrong. Any ideas on why this is?
```ts
import { queryOptions, useQueries } from "@tanstack/react-query";
...default mutation onError fallback?
Reset Mutation State in onError Handler of MutationCache
using queryFn callback arguments breaks type inference (if placeholderData is a function)
Experimental streaming without prefetching in Next.js
@tanstack/react-query-next-experimental and I understand that a new QueryClient is created for each server request.
However, on a single frontend route, I have both the layout and the page, which are server-side, and they make the same request to the backend.
Is there any alternative where I can cache these requests within the same frontend route?...
useInfiniteQuery blocks useQuery in modal
useInfiniteQuery. You can click each row to open a modal, which contains a useQuery to load additional data. My issue is that after initial load, it'll start loading the first next page, and while doing so, all useQuery calls in the modals are blocked. Upon completion, the modal loads immediately. Also, this doesn't seem to happen for subsequent next page loads. Does anyone know what might be going on? Am I not supposed to be calling useQuery from modals in...How to type select fn

OnSettled return void change in recent update causes error, how to solve?
void |Â Promise<void>it started to throw an error. How can we achieve the same result now?
I want to use use, and use query mutate
queryDefaults typing