fix(backfill): nest-build spec typing (unblocks #133 deploy) #134

root · 2026-06-12T11:47:16+03:00

root commented

2026-06-12 11:47:16 +03:00

Follow-up to #133. The prod nest build compiles spec files; the untyped queue mock made mock.calls[i] a 0-length tuple → build failed. Types the mock args as unknown[]. Tests 7/7, pnpm build green. No behaviour change.

Follow-up to #133. The prod `nest build` compiles spec files; the untyped queue mock made `mock.calls[i]` a 0-length tuple → build failed. Types the mock args as unknown[]. Tests 7/7, `pnpm build` green. No behaviour change.

root added 1 commit 2026-06-12 11:47:17 +03:00

fix(backfill): type spec queue mock so production nest build compiles it

QA Gate (P0/P1) / Test affected app (pull_request) Has been cancelled

Details

a7678acbe1

The prod docker build runs `nest build`, which compiles spec files too —
the untyped `vi.fn(async () => undefined)` mock made `queue.add.mock.calls[i]`
a zero-length tuple, so the destructures tripped TS2493/TS2352 and failed
`pnpm build` (tsc --noEmit had skipped the spec). Type the mock args as
unknown[]. No behaviour change; tests still 7/7, `pnpm build` green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

root merged commit 33e59c9554 into main

2026-06-12 11:47:25 +03:00

root referenced this issue from a commit

2026-06-12 11:47:27 +03:00

Merge pull request 'fix(backfill): nest-build spec typing (unblocks #133 deploy)' (#134) from fix/backfill-lifo-fast-lane into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: root/sase.tr#134