refactor(anatomy): category becomes free-form string, no enum / no auto-trigger
User asked that the app interact with anything carrying data-anno-* attributes without hardcoding any specific category, id, or name. Future SVGs may introduce new categories, and the existing SVGs may be updated. Changes: - `BoneCategory` is now `type BoneCategory = string`. The closed union is gone; the parser accepts any non-empty value. New categories don't require code changes. - `VALID_CATEGORIES` and `isValidCategory()` removed from svgConvention.ts. `validateBoneElement()` now only enforces presence of `data-anno-id` and `data-anno-category`. - EditorRoute no longer auto-triggers the vertebra picker when the clicked annotation is `zone-colonne`. Any zone is added the same way to the active observation regardless of category. - ObservationCard shows a "Vertèbres…" link on every zone badge (was conditional on `category === 'zone-colonne'`). The praticien picks vertebrae only when relevant — the UI no longer knows or cares which zones are spinal. - Tests rewritten: removed the `isValidCategory` enum assertions and the "rejects unknown category" branch. New test demonstrates that parseSvgBones accepts a completely novel category string. 90/90 tests pass, lint clean, build clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
cad94a49db
commit
21b678c3d5
5 files changed
+41
-76
No files matched your search
@@ -118,10 +118,6 @@ export default function EditorRoute() {
|
||||
)
|
||||
: [...activeObs.zones, newZone]
|
||||
updateObservation(activeIndex, { ...activeObs, zones: nextZones })
|
||||
|
||||
if (!exists && bone.category === 'zone-colonne') {
|
||||
setVertebraTarget(nextZones.length - 1)
|
||||
}
|
||||
}
|
||||
|
||||
async function onExport() {
|
||||
|
||||
Reference in new issue
Block a user