* add failing repro test
* update assertinos
* add logg
* ehm - maybe fix?
* rm -only
* make example
* upd
* ad debug logs
* more debugging
* push
* maybe???
* rm log
* revert
* fix: ?
* fix: check for pending status again
otherwise, we risk including promises that happen because of background updates (think persistQueryClient)
* fix: clear serverQueryClient between "requests"
otherwise, we are re-using the cache and the query won't be in "pending" state the second time around
* chore: remove logs
* rethrow next build error
* kick off ci again
* add `shouldRedactError` option
* pluralize
* docs
* chore: more memory
* chore: revert more memory
* don't compare statuses if they don't exist
* ci: apply automated fixes
* lint
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* feat: add queryClient to queryFunctionContext
* fix: remove queryClient exception
closing over a queryClient should now error, as we pass the queryClient directly to the queryFunctionContext
* fix: persister
* refactor: keep private reference to cache
* chore: fix tests
* docs: QueryFunctionContext
* refactor: derive from private member
* refactor: name it `client`
* refactor: let's go with client
* chore: try skipping the cache
* chore: re-enable caching
and try to bust it by changing sharedGlobals lol
* docs(svelte): fix writable stores tutorial link
Update the Svelte stores tutorial link to the correct URL in the Svelte Query overview documentation.
The previous link to writable-stores was broken or outdated.
* docs(ssr): update Next.js documentation links to latest version
Update outdated Next.js documentation links in the SSR guide to point to
the latest App Router documentation paths, ensuring users are directed to
the most current and relevant documentation.
Links updated:
- rewrites feature
- automatic static optimization
- rewrite parameters
* docs(react-query): Add import statement with skipToken to the docs
Makes more obvious how should the skipToken be used
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* feat(react-query): allow useQuery and useQueries to unsubscribe from the query cache with an option
* test: subscribed
* fix: revert calling getOptimisticResult later
* docs(react): update the react-native.md section (#8506)
* update the doc
* update the doc
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
* docs: reference
---------
Co-authored-by: Florian De la comble <f.delacomble@gmail.com>
* let’s do it again
* fix test group
* maybe
* mkay
* cool
* rm console.logs
* mkay
* mkay
* fix(vue-query): invalidate queries immediately after calling `invalidateQueries` (#7930)
* fix(vue-query): invalidate queries immediately after call `invalidateQueries`
* chore: recovery code comments
* release: v5.53.2
* docs(vue-query): update SSR guide for nuxt2 (#8001)
* docs: update SSR guide for nuxt2
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* thenable
* mkay
* Update packages/react-query/src/__tests__/useQuery.test.tsx
* mkay
* mkay
* faster and more consistent
* mkay
* mkay
* mkay
* mkay
* mkay
* fix unhandled rejections
* more
* more
* mkay
* fix more
* fixy
* cool
* Update packages/react-query/package.json
* fix: track data property if `promise` is tracked
if users use the `promise` returned from useQuery, they are actually interested in the `data` it unwraps to. Since the promise doesn't change when data resolves, we would likely miss a re-render
* Revert "fix: track data property if `promise` is tracked"
This reverts commit d1184babd1.
* add test case that @tkdodo was concerned about
* tweak
* mkay
* add `useInfiniteQuery()` test
* consistent testing
* better test
* rm comment
* test resetting errror boundary
* better test
* cool
* cool
* more test
* mv cleanup
* mkay
* some more things
* add fixme
* fix types
* wat
* fixes
* revert
* fix
* colocating doesn’t workkk
* mkay
* mkay
* might work
* more test
* cool
* i don’t know hwat i’m doing
* mocky
* lint
* space
* rm log
* setIsServer
* mkay
* ffs
* remove unnecessary stufffff
* tweak more
* just naming and comments
* tweak
* fix: use fetchOptimistic util instead of observer.fetchOptimistic
* refactor: make sure to only trigger fetching during render if we really have no cache entry yet
* fix: move the `isNewCacheEntry` check before observer creation
* chore: avoid rect key warnings
* fix: add an `updateResult` for all observers to finalize currentThenable
* chore: logs during suspense errors
* fix: empty catch
* feature flag
* add comment
* simplify
* omit from suspense
* feat flag
* more tests
* test: scope experimental_promise to useQuery().promise tests
* refactor: rename to experimental_prefetchInRender
* test: more tests
* test: more cancelation
* fix cancellation
* make it work
* tweak comment
* Update packages/react-query/src/useBaseQuery.ts
* simplify code a bit
* Update packages/query-core/src/queryObserver.ts
* refactor: move experimental_prefetchInRender check until after the early bail-out
* fix: when cancelled, the promise should stay pending
* test: disabled case
* chore: no idea what's going on
* refactor: delete unnecessary check
* revert refactor i did for cancellation when we wanted it to `throw`
* add docs
* align
* tweak
* Update docs/reference/QueryClient.md
* Update docs/framework/react/reference/queryOptions.md
---------
Co-authored-by: Alex Liu <dsa1314@gmail.com>
Co-authored-by: Tanner Linsley <tannerlinsley@users.noreply.github.com>
Co-authored-by: Damian Osipiuk <osipiukd+git@gmail.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
* feat(react-query-dev-tools): Add ReactQueryDevToolsPanel support
Devtools Embedded Support is finally here!
Embedded Mode will embed the devtools as a regular component in your application. You can style it however you'd like after that!
---------
Co-authored-by: Aryan Deora <adeora@iu.edu>
When copying the command, the $ appears in the copied text which makes a tiny text processing required - i.e removing the prefix. Instead of being able to just paste in a terminal and get going.
This mimics the behaviour of all commands everywhere else in the docs I could find. e.g https://tanstack.com/query/latest/docs/framework/react/installation