Files
accounted/app/api/bookkeeping/no-doc-required/batch/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

64 lines
2.2 KiB
TypeScript

import { NextResponse } from 'next/server'
import { z } from 'zod'
import { withRouteContext } from '@/lib/api/with-route-context'
import { validateBody } from '@/lib/api/validate'
import { markEntriesNoDocRequired } from '@/lib/bookkeeping/no-doc-required'
import { NEEDS_DOC_SOURCE_TYPES } from '@/lib/worklist/categories'
const BatchNoDocSchema = z.object({
journal_entry_ids: z.array(z.string().uuid()).min(1).max(500),
reason: z.string().trim().max(200).nullable().optional(),
})
/**
* Batch-mark posted verifikationer as "Inget underlag krävs". Lets the user
* clear many entries (e.g. historical SIE imports) out of "Att hantera: saknade
* underlag" in one action instead of toggling each one.
*
* The exemption is shared bookkeeping metadata (company-scoped, like mapping
* rules): the audit_log trigger records the actor.
*/
export const POST = withRouteContext(
'journal_entry.batch_no_document_required',
async (request, { supabase, companyId, user }) => {
const validation = await validateBody(request, BatchNoDocSchema)
if (!validation.success) return validation.response
const { journal_entry_ids, reason } = validation.data
// Defense in depth: only exempt posted entries that belong to this company.
// Validate ownership in chunks so the PostgREST `in()` URL stays bounded.
const ownedIds: string[] = []
for (let i = 0; i < journal_entry_ids.length; i += 200) {
const chunk = journal_entry_ids.slice(i, i + 200)
const { data, error } = await supabase
.from('journal_entries')
.select('id')
.eq('company_id', companyId)
.eq('status', 'posted')
.in('source_type', [...NEEDS_DOC_SOURCE_TYPES])
.in('id', chunk)
if (error) {
return NextResponse.json({ error: error.message }, { status: 400 })
}
ownedIds.push(...(data ?? []).map((r) => r.id))
}
if (ownedIds.length === 0) {
return NextResponse.json({ data: { exempted: 0 } })
}
const exempted = await markEntriesNoDocRequired(
supabase,
companyId,
user.id,
ownedIds,
reason ?? null,
)
return NextResponse.json({ data: { exempted } })
},
{ requireWrite: true },
)