Overview - Query

query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
dd901aef test(angular-query-experimental/injectQueries): add test for error state when one of the queries rejects (#10597)
by Wonsuk Choi
Failed
10523
54605bfd chore(deps): update all non-major dependencies
by renovate[bot]
Failed
9835
c9d46b83 Merge branch 'main' into implement-simplified-imperitive-methods
by Ciarán Curley
Failed
15
2da25e7c

u
Succeeded
fix/persister-query-key-noinfer
eb7c5a46 Merge 5f82c4ddc90df087b7b4de106cbae58bcfdc9b47 into dd901aef9803226a791f3f858114171ddeae7d70
by Neef Rehman
Succeeded
10601
5f82c4dd fix(query-core): restore NoInfer on persister's TQueryKey Follow-up to #10510. That PR removed NoInfer from all three persister generics to fix TQueryFnData inference when the companion queryFn declares a parameter (#7842). Keeping NoInfer on TQueryKey preserves that fix while preventing the persister slot from widening TQueryKey inference. Without NoInfer on TQueryKey, the persister slot contributes to TQueryKey inference. When Register.queryKey is augmented to a narrowed constraint, TQueryKey widens to that constraint instead of the literal passed to queryKey. Wrappers that brand their return with DataTag<TQueryKey, ...> then produce a brand on the wider type, which a plain literal tuple can no longer satisfy in contravariant positions (vi.mocked(...).mockReturnValue, typed variable assignments, etc.). TQueryFnData still participates in inference, so #10510's positive and negative type tests continue to pass.
by neefrehman
Succeeded
10593
c4a93ed5 Merge branch 'main' into fix/issue-9937
by Dominik Do...
Succeeded
main
2ab67ca1 Merge dd901aef9803226a791f3f858114171ddeae7d70 into 51ef23f46b23f9f7fd858386e42bfbb3adb5e49d
by pull[bot]
Succeeded
10599
2074bc35 ci(.github/workflows/pr): revert 'pkg-pr-new' pin after verifying Preview regression
by Wonsuk Choi
Succeeded
10599
80ce0337 ci(.github/workflows/pr): pin 'pkg-pr-new' to '0.0.66' to verify Preview regression
by Wonsuk Choi
Succeeded
test/angular-query-inject-is-restoring-add-injector-option-resolve-test
6fc5caf7 Merge fdcc540a747b1b2766176eff58d03559ac69d4cd into dd901aef9803226a791f3f858114171ddeae7d70
by Wonsuk Choi
Succeeded
test/angular-query-inject-is-restoring-add-injector-option-resolve-test
6fc5caf7 Merge fdcc540a747b1b2766176eff58d03559ac69d4cd into dd901aef9803226a791f3f858114171ddeae7d70
by Wonsuk Choi
Succeeded
10599
fdcc540a test(angular-query-experimental/injectIsRestoring): add test for resolving 'provideIsRestoring' value with 'injector' option
by Wonsuk Choi
Succeeded
103
c55573e3
by pull[bot]
Succeeded
main
441204b9 ci: Version Packages (#10582) ci: changeset release Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
10598
f6b63a04 fix(solid-query): skip reconcile when data reference is unchanged Previously, the reconcile path in useBaseQuery would invoke the user's reconcile callback (or the structural reconcile from solid-js/store) multiple times per logical query update — once for fetching=true transitions where the data reference had not changed, and again when the actual data resolved. With user-provided reconcile functions, this showed up as oldData === newData calls. Short-circuit reconcileFn when store.data === result.data; the rest of the result still flows through setState so isFetching/status updates keep working. Closes #8873
by Ousama Ben...
Succeeded
main
441204b9 ci: Version Packages (#10582) ci: changeset release Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
by github-act...
Succeeded
102
cd2d604e oups, missed the unstaged changes
by Thibaut Ti...
Succeeded
main
dd901aef test(angular-query-experimental/injectQueries): add test for error state when one of the queries rejects (#10597)
by Wonsuk Choi
Succeeded
65
aaa23a18 Fix several typos in README
by Denis Sikuler