Overview - Query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
1f84256a docs: document the `select` typing caveat for parallel-queries hooks (#10984) Inlining a `select` on a query object passed to `useQueries` / `useSuspenseQueries` can't infer its `data` argument from the sibling `queryFn` and falls back to `unknown` — a known TypeScript limitation (TanStack/query#6556). Document the two workarounds (annotate the `select` parameter, or define the query with the `queryOptions` helper) in the React docs, and add type tests guarding the behavior. Scoped to React for an easier review; the other framework adapters can follow the same pattern in separate PRs. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Succeeded
10984
f9b201eb Merge branch 'main' into docs/queries-select-typing
by Jonghyeon Ko
Succeeded
10722
14773dac Merge branch 'main' into fix/svelte-query-containers-typo
by Jonghyeon Ko
Succeeded
10956
903b6df2 Merge branch 'main' into fix/query-core-bugs-metadata
by Jonghyeon Ko
Canceled
10956
903b6df2 Merge branch 'main' into fix/query-core-bugs-metadata
by Jonghyeon Ko
Succeeded
10984
6d3de441 docs: document the `select` typing caveat for parallel-queries hooks Inlining a `select` on a query object passed to `useQueries` / `useSuspenseQueries` can't infer its `data` argument from the sibling `queryFn` and falls back to `unknown` — a known TypeScript limitation (TanStack/query#6556). Document the two workarounds (annotate the `select` parameter, or define the query with the `queryOptions` helper) in the React docs, and add type tests guarding the behavior. Scoped to React for an easier review; the other framework adapters can follow the same pattern in separate PRs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Canceled
10984
6d3de441 docs: document the `select` typing caveat for parallel-queries hooks Inlining a `select` on a query object passed to `useQueries` / `useSuspenseQueries` can't infer its `data` argument from the sibling `queryFn` and falls back to `unknown` — a known TypeScript limitation (TanStack/query#6556). Document the two workarounds (annotate the `select` parameter, or define the query with the `queryOptions` helper) in the React docs, and add type tests guarding the behavior. Scoped to React for an easier review; the other framework adapters can follow the same pattern in separate PRs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Succeeded
main
0298c909 test(query-core): keep setQueryData typecheck green on TypeScript 5.4 (#10985) Under TypeScript 5.4, `NoInfer<T>` can't match an inline object literal against the value branch of the `Updater` union in `setQueryData`, so it falls back to the function branch and reports the literal as excess properties (TS2353). TS >= 5.5 handles it correctly. This surfaces in the `test:types:ts54` legacy typecheck via the project reference chain (e.g. react-query-persist-client / react-query-devtools build query-core's test sources). It is normally masked by the Nx remote cache and only re-runs — and fails — when a dependent package's type inputs change, so it can land on `main` unnoticed. Annotate the value before passing it to `setQueryData` to sidestep the 5.4 limitation while preserving the assertions. Verified across TS 5.4–6.0. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Succeeded
10984
4b71638f Merge branch 'main' into docs/queries-select-typing
by Jonghyeon Ko
Succeeded
10985
8396e558 test(query-core): keep setQueryData typecheck green on TypeScript 5.4 Under TypeScript 5.4, `NoInfer<T>` can't match an inline object literal against the value branch of the `Updater` union in `setQueryData`, so it falls back to the function branch and reports the literal as excess properties (TS2353). TS >= 5.5 handles it correctly. This surfaces in the `test:types:ts54` legacy typecheck via the project reference chain (e.g. react-query-persist-client / react-query-devtools build query-core's test sources). It is normally masked by the Nx remote cache and only re-runs — and fails — when a dependent package's type inputs change, so it can land on `main` unnoticed. Annotate the value before passing it to `setQueryData` to sidestep the 5.4 limitation while preserving the assertions. Verified across TS 5.4–6.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Succeeded
solid-query-v6-pre
b970e5f8 chore(changeset): split solid-query into its own fixed group (#10983) solid-query is tracking the Solid 1 -> 2 breaking jump and is on a v6 pre-release line, while query-core and the other adapters remain on v5. Because all of react/core/vue/solid shared a single `fixed` group, the solid v6 beta changesets dragged every package in that group to 6.0.0-beta.5, even though no changeset targets them. Carve the three solid packages into their own `fixed` group so they can version independently on the v6 line. This mirrors the existing svelte group (already on 6.x while core stays on 5.x) and matches the agreed policy that version-syncing should happen across majors only -- no v6 beta of unaffected adapters. Verified with `changeset version` (prerelease mode): only solid-query, solid-query-devtools and solid-query-persist-client bump to 6.0.0-beta.5; query-core/react-query/vue-query stay at 5.101.0 and svelte-query stays at 6.1.34. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Failed
10984
51f4d08e docs: document the `select` typing caveat for parallel-queries hooks Inlining a `select` on a query object passed to `useQueries` / `useSuspenseQueries` can't infer its `data` argument from the sibling `queryFn` and falls back to `unknown` — a known TypeScript limitation (TanStack/query#6556). Document the two workarounds (annotate the `select` parameter, or define the query with the `queryOptions` helper) in the React docs, and add type tests guarding the behavior. Scoped to React for an easier review; the other framework adapters can follow the same pattern in separate PRs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Failed
10984
a573e028 docs: document the `select` typing caveat for parallel-queries hooks Inlining a `select` on a query object passed to `useQueries` / `useSuspenseQueries` can't infer its `data` argument from the sibling `queryFn` and falls back to `unknown` — a known TypeScript limitation (TanStack/query#6556). Document the two workarounds (annotate the `select` parameter, or define the query with the `queryOptions` helper) in the React docs, and add type tests guarding the behavior. Scoped to React for an easier review; the other framework adapters can follow the same pattern in separate PRs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Succeeded
10984
bb8f37a6 docs: document the `select` typing caveat for parallel-queries hooks Inlining a `select` on a query object passed to `useQueries` / `useSuspenseQueries` can't infer its `data` argument from the sibling `queryFn` and falls back to `unknown` — a known TypeScript limitation (TanStack/query#6556). Document the two workarounds (annotate the `select` parameter, or define the query with the `queryOptions` helper) in the React docs, and add type tests guarding the behavior. Scoped to React for an easier review; the other framework adapters can follow the same pattern in separate PRs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Failed
10984
8880f460 docs: document the `select` typing caveat for parallel-queries hooks Inlining a `select` on a query object passed to useQueries / useSuspenseQueries / createQueries / injectQueries can't infer its `data` argument from the sibling `queryFn` and falls back to `unknown` — a known TypeScript limitation (TanStack/query#6556). Document the two workarounds (annotate the `select` parameter, or define the query with the `queryOptions` helper) across the React, Preact, Solid, Vue, Svelte and Angular docs, and add type tests guarding the behavior in each framework. The caveat is surfaced via the React reference docs (shared with Solid/Vue), the shared parallel-queries guide (shared with Preact/Angular), and JSDoc `@remarks` on the Preact/Svelte/Angular source. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko
Succeeded
10983
fa5779a7 chore(changeset): split solid-query into its own fixed group solid-query is tracking the Solid 1 -> 2 breaking jump and is on a v6 pre-release line, while query-core and the other adapters remain on v5. Because all of react/core/vue/solid shared a single `fixed` group, the solid v6 beta changesets dragged every package in that group to 6.0.0-beta.5, even though no changeset targets them. Carve the three solid packages into their own `fixed` group so they can version independently on the v6 line. This mirrors the existing svelte group (already on 6.x while core stays on 5.x) and matches the agreed policy that version-syncing should happen across majors only -- no v6 beta of unaffected adapters. Verified with `changeset version` (prerelease mode): only solid-query, solid-query-devtools and solid-query-persist-client bump to 6.0.0-beta.5; query-core/react-query/vue-query stay at 5.101.0 and svelte-query stays at 6.1.34. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Jonghyeon Ko