Repository navigation
perf(api): count consolidation summaries without loading records - #1772
zack-dev-cm wants to merge 1 commit into
Conversation
Signed-off-by: zack-dev-cm <112114097+zack-dev-cm@users.noreply.github.com>
|
@zack-dev-cm is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Merged as part of #1811, which kept your commits and added review fixes on top (details in its description). Thanks for the contribution. |
The consolidation-status reader loads every stored summary just to count it. Use the existing key-list API for that count, keeping the value-list fallback for adapters or backends without key listing.
The existing recurring-pattern filtering, other collections' null handling, response shape and 30-second count cache are preserved. This addresses the summary-count path in #1735; the other count paths and list pagination remain separate.
Validation:
Refs #1735
Summary by CodeRabbit