From a7d02433d2d650ef8cb9a2c5fce4f6630d8f19fa Mon Sep 17 00:00:00 2001 From: Sergey Krylov Date: Wed, 4 Nov 2026 10:38:57 +0300 Subject: [PATCH] refactor: tidy tbank-sync claim comments (WealthLedger/backend#166) --- src/integrations/tbank/tbank-sync-claim.ts | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/src/integrations/tbank/tbank-sync-claim.ts b/src/integrations/tbank/tbank-sync-claim.ts index 10089f7..2445398 100644 --- a/src/integrations/tbank/tbank-sync-claim.ts +++ b/src/integrations/tbank/tbank-sync-claim.ts @@ -3,17 +3,13 @@ import type { TbankSyncAttempt } from './tbank-access.service'; const NO_UPDATED_ROWS = 0; -// Shared owners for the tbank-sync DB claim/lock protocol (backend#166). +// Shared owners for the tbank-sync DB claim/lock protocol. // Both helpers are CAS fences: they run inside the caller's transaction and // keep the exact where/data shapes they replaced. Callers keep deciding // success from the claim count exactly as before. // Claims the active TbankSyncWork row: only the still-running attempt of a // valid connection may transition. `data` is the state transition to apply. -// `state` overrides the default 'running' fence (e.g. an initiator row also -// accepts 'complete'); `withoutConnectionFence` drops the -// `connection: { invalidToken: false }` guard for fences that must also fire -// on an invalidated connection. export type ClaimOptions = { // Overrides the default 'running' fence (e.g. an initiator row also // accepts 'complete').