Docs Patterns
Taxonomy managerexperimental
Where the vocabularies live. Add values, deprecate them with a migration target, and see live usage counts — a value that titles still use can be deprecated but never silently deleted.
Guidelines
- mustRemove is disabled while usage > 0; the label says why ('Remove (in use)') instead of failing silently.
- mustDeprecation shows the live usage count in the confirm dialog and offers Undo in the toast.
- mustUsage counts come from the same records the tagger edits — never a second source of truth.
- shouldDuplicate value names are rejected case-insensitively at entry, with the error on the field.
- mustOpening a value navigates to /tagger?<facet>=<value> — the association surface. The filter renders there as a removable Chip, and the filtered empty state explains how to add the value to a title.
- mustVocabulary edits are workspace mutations: every add, deprecate, remove, and undo routes through the store, persists, and appends a real audit event (entityType Taxonomy) — never page-local state.
- mustUsage counts read the LIVE editorial sets, so tagging a title moves the taxonomy numbers immediately.
- mustDeprecated values disappear from authoring surfaces (tagger add selects) but remain in querying surfaces (search filters, rule builders) — titles may still carry them.