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>
53 lines
1.7 KiB
TypeScript
53 lines
1.7 KiB
TypeScript
import type { SupabaseClient } from '@supabase/supabase-js'
|
|
|
|
/**
|
|
* Per-company rate limiter for document-inbox ingestion. Backed by the
|
|
* `check_and_increment_inbox_quota` Postgres RPC (atomic check + increment),
|
|
* not Upstash: keeps the limiter on the same shared distributed store the
|
|
* rest of the app already hits, and works without extra env vars on Vercel
|
|
* and Docker self-hosters alike.
|
|
*
|
|
* Both windows are per-company:
|
|
* - MINUTE_MAX: a real user could only ever hit this with a script or by
|
|
* holding the upload button. The defense is against burst floods.
|
|
* - DAY_MAX: the backstop against slow drip abuse. A legitimate end-of-
|
|
* month batch is well under this number.
|
|
*/
|
|
export interface InboxLimitResult {
|
|
ok: boolean
|
|
retryAfterSec?: number
|
|
scope?: 'minute' | 'day'
|
|
}
|
|
|
|
const MINUTE_MAX = 30
|
|
const DAY_MAX = 500
|
|
|
|
export async function checkInboxUploadRateLimit(
|
|
supabase: SupabaseClient,
|
|
companyId: string,
|
|
): Promise<InboxLimitResult> {
|
|
const { data, error } = await supabase.rpc('check_and_increment_inbox_quota', {
|
|
p_company_id: companyId,
|
|
p_minute_max: MINUTE_MAX,
|
|
p_day_max: DAY_MAX,
|
|
})
|
|
if (error) {
|
|
// Fail open on infra error. The limiter is defense-in-depth: per-file
|
|
// size + MIME checks still apply on the upload route. Better to accept
|
|
// an upload than 500 a real user because Postgres blipped.
|
|
console.error('[inbox-rate-limit] RPC failed:', error)
|
|
return { ok: true }
|
|
}
|
|
// RPC returns jsonb_build_object payload. The JS client decodes as object.
|
|
const result = (data ?? { ok: true }) as {
|
|
ok: boolean
|
|
scope?: 'minute' | 'day'
|
|
retry_after_sec?: number
|
|
}
|
|
return {
|
|
ok: result.ok,
|
|
scope: result.scope,
|
|
retryAfterSec: result.retry_after_sec,
|
|
}
|
|
}
|