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
Suggestions on dynamic refetchInterval adjustment
refetchInterval
takes a function to allow it to be adjusted, which is great. I'm wondering what the suggested/ideal approach is for the following scenario:
What I'd like to achieve is to be able to trigger a more rapid refetch after a job is triggered by a button push, and then fall back to a more relaxed schedule once all the tasks associated with that job are complete. The idea here being that the UI should be more reactive when a job is ongoing, but in the interest of performance should slow down if nothing is happening.
The issue I'm encountering is that because I'd like to use a more relaxed interval as my default (30 seconds), it takes a long time to trigger the recalculation to switch over to the more rapid interval (5 seconds). I'd like the switch to be instantaneous....refetching from child component with typescript?
v3 -> v5 migration; issues with SSE
Invalidate query in react native
When is "select" function called exactly?
useQuery
call using useMemo
, which results in everything being called twice whenever there's a change.
I moved the code from useMemo
into a select
handler and extracted the handler to a stable function reference....TypeError: (0 , _tanstack_react_query__WEBPACK_IMPORTED_MODULE_2__.useQuery) is not a function
Error boundary does not seem to reset suspense query properly when leaving the page with the error.
Error Handling with Fetch works but isError always returns False

Mutation promise resolution
useInfiniteQuery not inferring types
react query vs redux toolkit query
useInfiniteQuery error
Error from axios how to handle it
Errors while using query in combination with table's subComponent ft.
Tracked Queries and Providers
useQuery
but doing so in a provider to pass this data around, does doing this ruin tracking and make react-query watch all variables?
Can you also give a good example of when and when not to be using queries in a provider. We typically call them in a provider, mix with some other logic and return data. Should this 'mix with other logic' typically happen within the queryFn and requirements for Provider passing the data is more of the edge case?...Mutation -> Invalidation + Refetch or setQueryData
next 13
dayBookQuery: (opts: DayBookOptionProps) => SWRResponse<SupabaseManyRowResult<T>, PostgrestError>;
dayBookQuery: (opts: DayBookOptionProps) => SWRResponse<SupabaseManyRowResult<T>, PostgrestError>;
react-queryv5 showing toast onSuccess
Client side error 400. What's wrong
useInfiniteQuery