* feat(solid-query): Rework internals of createBaseQuery
This change aims to simplify and enhance the internals of `createBaseQuery`.
This change is a precursor to fix a couple of pressing issues in solid-query mentioned in
#7079#7083#7173#7036#6620#6373
PRs for which are coming soon.
A key few highlights coming with this change:
1. Removal of `mutate` and `refetch` branches in `createClientSubscriber`: We had two different ways of resolving a query resource. The `mutate` option that optimistically updated a resource proved to be a problem with error queries. A query that has `placeholder` data and fails for any reason would see a flash of blank content before yielding to the ErrorBoundary. Using `refetch` for all query resolutions gives us a nice and simple way to transition to error boundaries
2. Removal of batched calls with `notifyManager`: With the new approach we dont need to batch anything. Everything is taken care of automatically. This removes all sideEffects from solid-query as a nice plus
3. Central place to update state: The new `setStateWithReconciliation` function provides a nice and easy way to make the `reconcile` option way more powerful
4. Only accessing the `data` property now would trigger Suspense boundary. Previously any property accessed on a query would trigger the suspense boundary. This was not intentional and has been fixed now
5. Proxied `data` doesn't jump between different values in most cases
The documentation is confusing and not clear about how to use dependent queries in Vue. This PR updates the documentation to make it clear and easy to understand.
discussion: https://github.com/TanStack/query/discussions/7220
* feat(core): memoize result of combine
this PR makes sure to only re-run the combine function if the function itself changed referentially or any of the inputs changed
* docs: combine memoization
* Update docs/framework/react/reference/useQueries.md
TanStack Router uses path-based navigation instead of route-based navigation, so many of the relative documentation links will be invalid after migration. This fixes that.
* fix(types): add pageParam and direction as optional to "normal" queryFn
because that's what we get when using a defaultQueryFn
* chore: remove tests that are no longer true
* chore: cleanup
* wth?
* fix(codemod): add support for useMutation
* fix(codemod): add missing empty line to test fixture file
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
* fix(react-query): infer data type correctly when conditional skipToken is passed to useQueries
* refactor: add OmitKeyof to useQueries.test-d.tsx
* fix(*): Ensure correct data type with conditional skipToken
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>