Overview - Query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
9656dc4e fix(query-core): Keep observer notifications stable (#11234) Removing an observer in place can shift the active notification loop and skip the next observer. Iterate over a shallow copy so synchronous unsubscriptions keep the old behavior without giving up the faster removal path from #11214. Co-authored-by: Codex <noreply@openai.com>
by Scott Cooper
Succeeded
11234
131504a8 fix(query-core): Keep observer notifications stable Removing an observer in place can shift the active notification loop and skip the next observer. Iterate over a shallow copy so synchronous unsubscriptions keep the old behavior without giving up the faster removal path from #11214. Co-Authored-By: Codex <noreply@openai.com>
by Scott Cooper
Succeeded
main
1f631b36 perf(query-core): Skip unused query result tracking (#11225) * perf(query-core): Skip unused query result tracking QueriesObserver was building tracked results on every update even when there was no combine function to consume them. Skip that work for normal useQueries notifications. Co-Authored-By: Codex <noreply@openai.com> * ref(query-core): Reuse combine skip check Treat a missing combine function as another reason to skip combining. This keeps the notification flow close to the existing code and only defers result tracking. Co-Authored-By: Codex <noreply@openai.com> * ref(query-core): Match combine presence check Use the same truthiness check as combineResult so null and other falsy runtime values follow the existing no-combine behavior. Co-Authored-By: Codex <noreply@openai.com> --------- Co-authored-by: Codex <noreply@openai.com> Co-authored-by: Dominik Dorfmeister 🔮 <office@dorfmeister.cc>
by Scott Cooper
Succeeded
main
5bb089d1 perf(query-core): Reduce observer removal overhead (#11214) Removing observers copied the full observer list on every unsubscribe, which got expensive when thousands of components shared a query. Splice the existing list in place instead. Co-authored-by: Codex <noreply@openai.com> Co-authored-by: Dominik Dorfmeister 🔮 <office@dorfmeister.cc>
by Scott Cooper
Succeeded
main
01a02bfa perf(query-core): Deduplicate tracked query properties (#11215) * perf(query-core): Deduplicate tracked query properties Each accessed useQueries result fans the same property out to every observer, making ordinary result mapping quadratic. Track which properties have already been synchronized during the current result pass. This keeps the #7000 behavior while dropping the 10,000-result tracking benchmark from about 699 ms to under 1 ms locally. Co-Authored-By: OpenAI Codex <noreply@openai.com> * test(query-core): Cover repeated property tracking Extend the existing tracking assertion to cover the same property being read from a second result. Co-Authored-By: OpenAI Codex <noreply@openai.com> --------- Co-authored-by: OpenAI Codex <noreply@openai.com> Co-authored-by: Dominik Dorfmeister 🔮 <office@dorfmeister.cc>
by Scott Cooper