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>
32 lines
1.2 KiB
TypeScript
32 lines
1.2 KiB
TypeScript
import { NextResponse } from 'next/server'
|
|
import { withRouteContext } from '@/lib/api/with-route-context'
|
|
import { BAS_REFERENCE } from '@/lib/bookkeeping/bas-reference'
|
|
|
|
/**
|
|
* GET /api/bookkeeping/accounts/bas-catalog
|
|
*
|
|
* The full BAS 2026 catalogue (~1,276 accounts), projected to the fields the
|
|
* AccountCombobox needs to search and render. This lets the manual bookkeeping
|
|
* flow surface accounts by name even when they aren't in the company's chart
|
|
* yet: selecting one routes through the existing activate-on-commit rail
|
|
* (ACCOUNTS_NOT_IN_CHART → ActivateAccountsDialog → /accounts/activate).
|
|
*
|
|
* The payload is static reference data for the deploy and identical for every
|
|
* company, so it's cached hard on the client. Wrapped in withRouteContext so it
|
|
* stays behind auth (MFA on hosted) like every other bookkeeping route.
|
|
*/
|
|
export const GET = withRouteContext('bookkeeping.accounts.bas_catalog', async () => {
|
|
const data = BAS_REFERENCE.map((a) => ({
|
|
account_number: a.account_number,
|
|
account_name: a.account_name,
|
|
account_class: a.account_class,
|
|
account_group: a.account_group,
|
|
description: a.description,
|
|
}))
|
|
|
|
return NextResponse.json(
|
|
{ data },
|
|
{ headers: { 'Cache-Control': 'private, max-age=86400' } },
|
|
)
|
|
})
|