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
Double fetching with React Router
i have been watching some tutorials on useQuery and everyone seems to use `isLoading`, my issue is t
isLoading, my issue is that when a refetch happens i need to also watch for isRefetching in order for my component to update with new data (after calling invalidateQueries), am i doing something wrong ? i was thinking about using fetchStatus instead of isLoading and but i am not sure if this will lead to some useless re-renders
in some component i call queryClient.invalidateQueries(), then i go to another page (using react-router-dom HashRouter) which should update with new data, i see the api call with the fresh data
a simple code example...how to implement setQueryData ??

Refetch all the queries on mutation
polling implementation with POST and GET endpoints
Merge results from different keys
export const useTodos = (todoIds) => useQuery({ queryKey: ['todos', todoIds], queryFn: fetchTodos(todoIds) })...Optimistic updates triggered
How to not show Axios errors in console?
invalidate multiple queries
React query prefetching does not work properly
React test stuck on `isLoading` condition
background sync react query
Any guidance / examples on react-query + handling live websocket events?
Custom useQuery Typesafe
Building JSON Objects
How can my query not exist in the queryClient?
OnSuccess alternative
onSuccesscallback like this:
```js
const { isLoading, mutateAsync } = useMutation({
mutationFn: CreateProduct,...One Quick Question Please.
Manipulate a query's data in Devtools
Building with Turbo/PNPM/Vite and Orval results in double context
apps/web-next and our Orval API get's generated at packages/bff-api. react-query is setup as a peer dependency inside bff-api but it is important to note: we do not actually build this bff-api package separately. It is basically just source code and our Vite build inside apps/web-next picks it up as such....