Jakob WennbergandClaude Sonnet 5
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>
31 lines
1.3 KiB
TypeScript
31 lines
1.3 KiB
TypeScript
import { NextResponse } from 'next/server'
|
|
import { withRouteContext } from '@/lib/api/with-route-context'
|
|
import { getJournalEntryUnderlagReferences } from '@/lib/core/bookkeeping/journal-entry-references'
|
|
|
|
/**
|
|
* GET /api/bookkeeping/journal-entries/[id]/references
|
|
*
|
|
* Resolves the verifikation's followable underlag references, the linked
|
|
* customer / supplier invoices that identify the affärshändelse. Lets the
|
|
* verifikat view make the verifieringskedja traceable from the verifikat side,
|
|
* not only from the invoice side (BFL 5 kap 7§, hänvisning till underlag;
|
|
* BFNAR 2013:2). Read-only.
|
|
*
|
|
* An id that doesn't belong to the active company resolves to no references
|
|
* (every underlying query is company-scoped), so this neither leaks nor 404s.
|
|
*
|
|
* Marked private, no-store: the payload carries invoice numbers (financial
|
|
* data), so no shared proxy / CDN may cache it across users or companies.
|
|
*/
|
|
export const GET = withRouteContext<{ params: Promise<{ id: string }> }>(
|
|
'journal_entry.references',
|
|
async (_request, { supabase, companyId }, { params }) => {
|
|
const { id } = await params
|
|
const references = await getJournalEntryUnderlagReferences(supabase, companyId, id)
|
|
return NextResponse.json(
|
|
{ data: { references } },
|
|
{ headers: { 'Cache-Control': 'private, no-store' } },
|
|
)
|
|
},
|
|
)
|