Skip to content

test: provide conditions for lens count-scope regressions - #95

Draft
agreenspan wants to merge 1 commit into
mainfrom
claude/api-count-test-conditions-20260906
Draft

test: provide conditions for lens count-scope regressions#95
agreenspan wants to merge 1 commit into
mainfrom
claude/api-count-test-conditions-20260906

Conversation

@agreenspan

Copy link
Copy Markdown
Contributor

Two lensWhere integration tests failed before reaching their soft-delete assertions because their atLeast rules omitted the required inner condition. The count API deliberately treats that omission as an authoring error in both json-rules 2.20.0 and 2.21.0.

Add condition: true to mean count every candidate child. Keep both database assertions unchanged: a tombstoned Contact cannot satisfy the count, and Session counting works without a deletedAt column. The production scope implementation remains responsible for live-row filtering.

Validation: all 1,006 API tests pass against the existing locked dependencies after configuring the local MinIO test environment. API typecheck passes. Adversarial review confirmed the two rules preserve the intended test semantics. bun run check still stops at 134 existing lint errors in unchanged files, so this PR is draft pending the repository-wide gate.

No dependency versions, production code, CI rules or CI fixtures changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant