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
how would you do this without the useQuery's onSuccess callback?
category field. I want to add a filter so the user can toggle the display of rows in certain categories. Prior to this major change talk i would reach for the onSuccess to set some filter state.
```tsx
onSuccess: (data) => {
const categoryState: Record<string, boolean> = {}...auto get Error ?

Looking for advice on how to debug intermittent bug related to query invalidation
Awaiting data with Suspense in Next?
Suspense like this and I get the error form the image
What's a robust way to define a dependent query when using `useQueries`?
useQueries for parallel queries that are based on a dependent list of unknown length. Normally dependent queries would use the enabled option to specify whether or not the prerequisite data is ready to allow the query to run, but that's not an option at the top level for useQueries. I saw on the github forums that you can pass an empty array to it to have it do a no-op but my concern with that is that the not yet loaded state then looks identical to an empty list respon...Ho to enhance previous response. Now that the on success is not accessible.
select propType in Typescript?

After mutation InvalidateQueries Doesn't work
Problems with comments and posts. Help!
What is the purpose of having `cacheTime` set to a higher value than `staleTime`?
cacheTime value controls how long data is kept in the in-memory cache before being garbage collected. The staleTime value controls how long cached data is considered fresh. Once this time expires, any requests will data will trigger a new fetch. By default, cacheTime is set to 5 minutes, and staleTime is set to 0 (meaning cached data is never fresh).
It seems like this configuration (or any configuration where cacheTime > staleTime) is kind of pointless. Why would you keep data persisted in the cache that you know is stale? Is there some scenario where having known-stale data provides a benefit over having the cache entry for that value be null?
Conversely, it also seems pointless to have cacheTime < staleTime, since in that scenario would result in cache misses for "fresh" data that had been garbage collected....Errors during the build process on vercel
I'm getting this error when i try to configure React Query in Next JS

Create and Get Queries outside of components
useQuery provides outside of a component.
I saw that I can use the setDefaultQuery-Fn from my queryClient.
What can I to call to retrieve that object?
More context:...Only fetch on "initial" load
PersistQueryClientProvider to cache data to local storage, so in case the initial new fetch fails, I still have a back-up. I've added cacheTime: Infinity and staleTime: Infinity to the UseQueryOptions of the specific fetch, however, now it only initially fetches once and then never again.
Thus I feel I have to invalidate the query (make it stale) whenever the app closes or perhaps when it initially loads. Not sure what is the best approach here....Newbie needs advice on how to structure query keys in this type of application
fetchStatus stuck in paused
Is there a `useIsFetching` for all queries within a specific component and its children?
Having difficult using useQuery with generics

Undefined data returned from useQuery hook
Does `useMutation().mutate()` batch calls to `onSuccess`?
create-person endpoint.
So I loop over this array and create a bucket of Promises using the mutations returned from useMutation() - they are all the same call in the end. I add a onSuccess callback. The code looks something like this:
```ts...