Files
accounted/app/api/rot-rut/eligible/route.ts
T
Jakob WennbergandClaude Sonnet 5 ec27228a8e style: remove em/en dashes repo-wide, add CLAUDE.md rule against them (#890)
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>
2026-07-04 15:58:06 +02:00

32 lines
1.2 KiB
TypeScript

import { NextResponse } from 'next/server'
import { withRouteContext } from '@/lib/api/with-route-context'
import { errorResponse } from '@/lib/errors/get-structured-error'
import { listRotRutCandidates } from '@/lib/invoices/rot-rut-service'
/**
* GET /api/rot-rut/eligible?type=rot|rut
*
* Lists paid invoices carrying a ROT/RUT claim that are NOT yet part of an
* active begäran om utbetalning, split into:
* - eligible: ready for file generation (with the amounts the file will use)
* - blocked: excluded, with the exact blocker (same evaluation as the
* generator: what this endpoint approves, the file accepts)
*/
export const GET = withRouteContext('rot_rut.eligible', async (request, ctx) => {
const { supabase, companyId, log, requestId } = ctx
const { searchParams } = new URL(request.url)
const typeParam = searchParams.get('type')
const type = typeParam === 'rut' ? 'rut' : 'rot'
const result = await listRotRutCandidates(supabase, companyId!, type)
if (!result.ok) {
log.error('failed to list rot/rut candidates', result.dbError as Error)
return errorResponse(result.dbError, log, { requestId })
}
return NextResponse.json({
data: { type, eligible: result.eligible, blocked: result.blocked },
})
})