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>
65 lines
2.3 KiB
TypeScript
65 lines
2.3 KiB
TypeScript
import type { Sector, SectorSlug, ExtensionDefinition } from './types'
|
|
import { EXTENSION_DEFINITIONS } from './_generated/sector-definitions'
|
|
import { WORKSPACES } from './_generated/workspace-map'
|
|
|
|
// ============================================================
|
|
// Sector & Extension Registry
|
|
// ============================================================
|
|
//
|
|
// Sector shells are structural and always present.
|
|
// Extension definitions per sector come from the generated file
|
|
// (controlled by extensions.config.json).
|
|
// ============================================================
|
|
|
|
/** Sector shells: structural metadata, always available */
|
|
const SECTOR_SHELLS: Omit<Sector, 'extensions'>[] = [
|
|
{
|
|
slug: 'general',
|
|
name: 'Generella verktyg',
|
|
icon: 'Layers',
|
|
description: 'Verktyg som passar alla verksamheter',
|
|
},
|
|
]
|
|
|
|
/** Full sectors with extensions merged from generated definitions */
|
|
export const SECTORS: Sector[] = SECTOR_SHELLS.map(shell => ({
|
|
...shell,
|
|
extensions: EXTENSION_DEFINITIONS[shell.slug] ?? [],
|
|
}))
|
|
|
|
// ============================================================
|
|
// Helper functions
|
|
// ============================================================
|
|
|
|
export function getSector(slug: SectorSlug): Sector | undefined {
|
|
return SECTORS.find(s => s.slug === slug)
|
|
}
|
|
|
|
export function getExtensionDefinition(sectorSlug: string, extensionSlug: string): ExtensionDefinition | undefined {
|
|
const sector = SECTORS.find(s => s.slug === sectorSlug)
|
|
return sector?.extensions.find(e => e.slug === extensionSlug)
|
|
}
|
|
|
|
export function getAllExtensions(): ExtensionDefinition[] {
|
|
return SECTORS.flatMap(s => s.extensions)
|
|
}
|
|
|
|
export function getExtensionsBySector(slug: SectorSlug): ExtensionDefinition[] {
|
|
return getSector(slug)?.extensions ?? []
|
|
}
|
|
|
|
/** Extensions with a workspace and a quickAction href, for sidebar nav. */
|
|
export function getExtensionNavItems(): { href: string; label: string; icon: string }[] {
|
|
return getAllExtensions()
|
|
.filter(e => {
|
|
const key = `${e.sector}/${e.slug}`
|
|
return key in WORKSPACES && !!e.quickAction?.href
|
|
})
|
|
.sort((a, b) => (a.quickAction!.order ?? 0) - (b.quickAction!.order ?? 0))
|
|
.map(e => ({
|
|
href: e.quickAction!.href!,
|
|
label: e.quickAction!.label,
|
|
icon: e.quickAction!.icon,
|
|
}))
|
|
}
|