Jakob Wennberg
ec27228a8e
Em dashes (—) and en dashes (–) had spread across comments, docs, tests, and a few UI strings, reading as AI-generated boilerplate rather than house style. Replaced each with punctuation matching its context: colon for explanatory clauses, comma for asides, plain hyphen for numeric/legal ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for paired-dash asides. messages/en.json and messages/sv.json were fixed by hand together to keep sv/en in sync. Left untouched where the dash is the functional subject rather than decorative punctuation: date-range-parser.ts's separator regex, charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the agent system-prompt files that already instruct against em dashes, and a golden iXBRL test fixture compared byte-for-byte. Also fixes two bugs surfaced along the way: an off-by-one in ApiKeysPanel's scope-label split (a leftover from an earlier partial pass), and a charset-repair test that had lost the literal en-dash it exists to verify. Regenerated the agent atom seed migration (skills:generate) since 27 SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes, with an explicit carve-out for the functional-dash cases above. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
45 lines
1.2 KiB
TypeScript
45 lines
1.2 KiB
TypeScript
import type { SupabaseClient } from '@supabase/supabase-js'
|
|
|
|
type MatchAction =
|
|
| 'matched'
|
|
| 'unmatched'
|
|
| 'auto_suggested'
|
|
| 'suggestion_cleared'
|
|
| 'storno_conflict_resolved'
|
|
| 'linked_to_existing_voucher'
|
|
|
|
/**
|
|
* Log a payment match event to the append-only audit trail.
|
|
* Fire-and-forget: never throws, never blocks the caller.
|
|
*/
|
|
export async function logMatchEvent(
|
|
supabase: SupabaseClient,
|
|
userId: string,
|
|
transactionId: string,
|
|
action: MatchAction,
|
|
opts?: {
|
|
invoiceId?: string
|
|
supplierInvoiceId?: string
|
|
matchConfidence?: number
|
|
matchMethod?: string
|
|
previousState?: Record<string, unknown>
|
|
newState?: Record<string, unknown>
|
|
}
|
|
): Promise<void> {
|
|
try {
|
|
await supabase.from('payment_match_log').insert({
|
|
user_id: userId,
|
|
transaction_id: transactionId,
|
|
invoice_id: opts?.invoiceId ?? null,
|
|
supplier_invoice_id: opts?.supplierInvoiceId ?? null,
|
|
action,
|
|
match_confidence: opts?.matchConfidence ?? null,
|
|
match_method: opts?.matchMethod ?? null,
|
|
previous_state: opts?.previousState ?? null,
|
|
new_state: opts?.newState ?? null,
|
|
})
|
|
} catch {
|
|
// Non-critical: audit log insert must never break the main flow
|
|
}
|
|
}
|