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
useQuery inside webworker/sharedWorker
Guessing there is no way to prefetch when using app-memory accessTokens
Query context hook changes and triggers rerender of my component

UseQuery data undefined in the components

isError always set to False, react query with axios
Creating a POST as a useQuery ( orval.dev )
How do I make useMutation call with time interval?
how to prevent onMount call ?

run some stateful code before each query and mutation
authToken has expired and use a method returned by my useContext(authContext) if it has) before each query and mutation. What would be the recommended way to do it? Any prop from QueryClienyProvider where i could place such logic?How do I use graphql mutations with the generated queries?
issues with dnd-kit using React Query (fetched list jumps each time a list item is reordered) (trpc)
the gist of the code is ```ts // fetches and renders the list (near identical to the docs) const BasicListEditor = () => {...
Data set with setQueryData is garbage collected (gets thrown out upon page refresh)
Why is `isLoading` initialized to `false` instead of `true` for queries with `placeholderData`?
status (which isLoading is derived from) say loading is enabled when "there's no cached data and no query attempt was finished yet." However, the docs for placeholderData say "placeholderData is not persisted to the cache"
So what's going on?
My use case is I have a query which I would like to initialize with placeholderData during initial load, but still have a correct initial isLoading flag set to false...useQuery data is undefined even with initialData/placeholderData
useQuery that fetches the options for a select input. I have tried with both initialData and placeholderData set as an empty array (which typewise is not incorrect, since I can have a select without options until they are added), but the data returned is set always set as <T | undefined> with T being the type of the options... Does it still require me to validate if isSuccess is true in order to set the type to T even though I have set the "default data"?
- @tanstack/react-query v4.24.4
- typescript v4.9.5...setQueryData returned by useQuery
UseQueries make Semantic Modal take a while to display
Query.isEnabled?
Pros and cons of query destructuring
const { data: myData } = useMyQuery()) vs naming the query and using it as is (const myQuery = useMyQuery()). We currently destructure everything, but it seems cumbersome when there are multiple queries in the same component because you have to remap every query prop to a different const - we end up having isQuery1Error, isQuery2Error etc.WebSocket integration
Use toggle to enable different useMutation call