Files
accounted/app/api/rot-rut/payout-requests/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

42 lines
1.5 KiB
TypeScript

import { NextResponse } from 'next/server'
import { withRouteContext } from '@/lib/api/with-route-context'
import { errorResponse } from '@/lib/errors/get-structured-error'
/**
* GET /api/rot-rut/payout-requests
*
* Request history (all statuses), newest first, with per-invoice items.
*/
export const GET = withRouteContext('rot_rut.requests.list', async (request, ctx) => {
const { supabase, companyId, log, requestId } = ctx
const { searchParams } = new URL(request.url)
const typeFilter = searchParams.get('type')
// Explicit projections: the history list needs identifiers and amounts,
// not every column (and never customer ids through the invoice join).
let query = supabase
.from('rot_rut_payout_requests')
.select(
'id, name, deduction_type, status, requested_total, decided_total, file_name, file_document_id, ' +
'created_at, submitted_at, decided_at, settlement_journal_entry_id, ' +
'items:rot_rut_payout_request_items(id, invoice_id, requested_amount, decided_amount, ' +
'invoice:invoices(id, invoice_number))',
)
.eq('company_id', companyId!)
.order('created_at', { ascending: false })
.limit(100)
if (typeFilter === 'rot' || typeFilter === 'rut') {
query = query.eq('deduction_type', typeFilter)
}
const { data, error } = await query
if (error) {
log.error('failed to list rot/rut payout requests', error)
return errorResponse(error, log, { requestId })
}
return NextResponse.json({ data })
})