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>
22 lines
960 B
TypeScript
22 lines
960 B
TypeScript
/**
|
|
* Personnummer masking for v1 list/create responses.
|
|
*
|
|
* GDPR Art.5(1)(c): data minimisation. A Swedish personnummer is a
|
|
* national identifier; the list endpoint and create-response shape mask
|
|
* the last 4 digits (the gender + checksum) so a roster scan or a
|
|
* mistaken response log doesn't leak a natural-person identifier. The
|
|
* detail endpoint (deliberate drill-in) returns the full value.
|
|
*
|
|
* Format: ÅÅÅÅMMDDNNNN → ÅÅÅÅMMDDXXXX.
|
|
*
|
|
* Defensive behavior: if the input is not exactly 12 digits, the full
|
|
* value is redacted to all-X. A short-form (10-digit) personnummer
|
|
* should never reach the database (the schema regex rejects it), but
|
|
* legacy rows or test fixtures might; redacting entirely is safer than
|
|
* leaking a partially-masked legacy value.
|
|
*/
|
|
export function maskPersonnummer(pnr: string | null | undefined): string {
|
|
if (!pnr || !/^\d{12}$/.test(pnr)) return 'XXXXXXXXXXXX'
|
|
return `${pnr.slice(0, 8)}XXXX`
|
|
}
|