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
Best Practices for Using tanstack-react-query with GraphQL in a Monorepo Structure
shared-features
. This package contains features, which uses react-query. I'm using GraphQL, so I can't just use a defaultQueryFn. I need a way to inject a query-fn.
Here's my current setup at the main-app, which should consume the shared-features
-package.
```js...`useInfiniteQuery` stalls at 'pending' status in NextJS App
useInfiniteQuery
which helps me get some data which I want to render out on the screen.
Here's what I'm currently trying:
```typescript
export const useGetLodgesInfinite = (payload?: LodgeService.GetLodgesPayload) => {...
When my useQuery is in error state, it seems to auto refetch.
data not getting updated immediately
useForm defaultvalues
What data strategy should I use?
Is it possible to call a mutation inside of a Next.js server component?
queryClient.fetchQuery
but there doesn't appear to be a similar method on queryClient
....Refetch mutation after user action.
Is there a way to persist data like `useInfiniteQuery` does, but for parallel queries?
data from useInfiniteQuery hook returning undefined despite the API correct returning it
data
property from the useInfiniteQuery
is returning as undefined
even with the response
returning the correcta data. Does anyone know the reason?im using react query 3. how can i get the data for a set of queries or the is loaded/successful
Knowing the current page of `useInfiniteQuery`
timestamp
and query
, so we can bi-directionally search. Is there a good way of knowing what our current page
is? I've skimmed the docs and probably missed something but the only thing that comes to mind is a local state variable.Implementing Data Polling with Stale Data in Next.js 14 using React Query

queryKey works as string but not with number
detail: (id: number) => ['decks', 'item', id],
When I make an edit mutation I got a result from the server, where id is number. So i use setQueryData with it....Failing to integrate react-query devtool triggers with tanstack-router
Avoid firing useQuery on every render
Suggestion for accessing useQuery data
How to initiate search params from initial api response without triggering re-fetch?
useQuery
and no search params that are passed down as args and part of queryKey
2. Endpoint returns initial parameters.
3. I add these initial parameters as search params to the URL
4. I retrieve these params via useSearch
from the router to show UI based on it it
5. Since search params also feed the useQuery
and now that params exist, queryKey
s changed, and data is fetched again...fetch "get" data in form submit
invalidateQueries / setQueryData post mutation not triggering the rerender of all consumers