Files
accounted/extensions/general/mcp-server/resources/vat-treatments.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

39 lines
1.5 KiB
TypeScript

import type { McpResource } from './types'
import { getAvailableVatRates, getVatRules } from '@/lib/invoices/vat-rules'
import type { CustomerType } from '@/types'
const CUSTOMER_TYPES: CustomerType[] = ['individual', 'swedish_business', 'eu_business', 'non_eu_business']
export const vatTreatmentsResource: McpResource = {
uri: 'Accounted://settings/vat-treatments',
name: 'VAT Treatments',
description: 'Available VAT treatments and rates per customer type, and the resulting moms ruta on the VAT declaration. Use before creating invoices to pick the right VAT rate.',
mimeType: 'application/json',
read: async () => {
const matrix: Record<string, unknown> = {}
for (const ct of CUSTOMER_TYPES) {
matrix[ct] = {
unvalidated_vat: {
rates: getAvailableVatRates(ct, false),
default_rule: getVatRules(ct, false),
},
validated_vat: {
rates: getAvailableVatRates(ct, true),
default_rule: getVatRules(ct, true),
},
}
}
return {
treatments: ['standard_25', 'reduced_12', 'reduced_6', 'reverse_charge', 'export', 'exempt'],
by_customer_type: matrix,
notes: {
eu_business_validated: 'Reverse charge applies: invoice 0%, customer self-accounts via moms ruta 39.',
non_eu_business: 'Export: invoice 0%, no Swedish VAT, moms ruta 40.',
mixed_rate: 'Invoice line items can have individual VAT rates; the engine generates per-rate lines.',
},
}
},
}