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
Get value from query hook or pass via props?
Query client on SSR memory
keep delivery token secure
persistQueryClient support suspense?
How to refetch partial data?
useQuery hook that calls my api which returns an object like this:
```json
{
"invites": [...],...on* callbacks alternative
onSuccess) will be deprecated in the next major version. Unfortunately I didn't find any alternative on the v5 Roadmap. How will it look like?What happens to refetchInterval when we call refetchQueries ?
Save & use data from local storage as initialdata and only fetch if data is not in ls
enabled: authenticated
- Save the fetched data in local storage
-- This I do in the onSuccess function...useMutationState `has no exported member named`

Mutation forcing me to pass some data
React Native 429 error
how do I prefetch the next page?

Next 13.4 - No QueryClient set
_app.tsx file in app folder and put what's in the SSR section of RQ documentation.
Created page.tsx inside folder called 1 inside app folder and just used react query like I used to: const query = useQuery({ queryKey: ['todos'], queryFn: () => axios.get('/any/thing') }). And only thing I get is: Error: No QueryClient set, use QueryClientProvider to set one...
Why does query not re-execute after Key changes?
findOfferForm.zipvalue changes?
```ts
const citiesQuery = useQuery({
queryKey: ['getLocationsByZipcode', findOfferForm.zip],...Query Key Factory type not inferred for old data in queryClient.setQueryData

Why does react-query devtools makes my component disappear?
preFetchQuery data isn't being used
Seeking suggestions for React Query folder structure

Optimistic update reverting back to cache
onSettled function
it will make a fetch request to the disk cache instead of server and that returns previous data.
...Callback after final mutations when dealing with consecutive mutations
mutation.mutate lets you pass in an onSuccess which only runs after the last mutation in a series of mutations is complete (think removing rows from a server-data driven table). However, as also mentioned in the docs, there are situations where that onSuccess won't be called (i.e. the overlay that calls the mutation unmounts). Is there a way to get the same behavior with the onSuccess passed into useMutation?
The goal is to only invalidate relevant queries once the series of mutations is complete. If I invalidate after every mutation alongside optimistic updates, it ends up with some fun back and forth in the UI. I can whip up a codesandbox if needed....