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
Mutation to tackle state update race conditions. Good or bad idea?
updateConfig called multiple times race condition can happen.
```typescript...Non-undefined placeholderData types as possibly undefined
placeholderData function always returns a proper result (not undefined), then why is the resulting data property typed as T | undefined?
Consider the following example:
```typescript...Using component state values in useMutation.mutate (closure/race condition help)
Why data value of queries is not updated on queryClient.setQueryData(['grid'], updatedGrid)
setQueryData causing the isDirty function to pretend data is always dirty even after saving data server side.
Query code :
```Typescript
export const useUpdateGrid = () => {...
React Query + MobX — can I (should I?) mutate query cache data directly?
Query data becomes inactive when switching views (useQuery vs. useQueries with shared queryKey)
reference variables in useMutation Key
useQuery() Typescript says only data is returned, not | undefined?

Advice for creating query "middle ware"
Issue with Normalization and Performance in Infinite Query with Large Datasets
Can I normalize every queryKey globally?
How to use the startTransition from react?
Multiple / dynamic number of query clients?
Is there a way to reset mutations based on key?
Is there a built-in way to refetch/invalidate queries based on a mutation being successful?
QueryObserver: duplicate queries found warning
[QueriesObserver]: Duplicate Queries found. This might result in unexpected behavior.
[QueriesObserver]: Duplicate Queries found. This might result in unexpected behavior.
Keep running useMutations while tab is not visible

useMutation for creating object to use with POST
Understanding the default error type in v5.
throw 5. I log the error and is indeed 5 with type number but the error type is annotated as Error | null. This can introduce runtime errors when narrowing the union and performing operations on the value such as
```tsx
// jobQuery.error is Error | null;
if (jobQuery.error === null) return...Best way to "trigger" mutation on Page Load?