v1.6.0
What's Changed
Added
- Fields overview + canonical fields API (#95, ADR-0002). Both field-definition doctrines
(legacy twig-annotationtitle, definition-kit sibling<id>.yamllabel) normalise
server-side into one canonical, ordered fields list; every other authored key (mcp,wp:,
visible_when, constraints, …) passes through the API verbatim — open contract, see
docs/API.md§ Fields. New sidebar entry Fields (/fields, shown when any component
declares fields viacatalog.hasFields): global searchable overview — filterable by field
key/label/type or component name — with click-through to the component
(/component/<id>?fields=1opens the drawer).FieldsDrawer/FieldsTablerender labels from
both doctrines and expand per-row verbatim detail. Malformed field entries are skipped rather
than failing the whole component, surfacing instead as a warning viaGET /styleguide/api/health.
Changed
/api/components+/api/fields:fieldsis now the canonical list (was: raw YAML map
pass-through), same on/api/pages//api/docs— the sameField[]shape
({ key, label, type, description, required, children, ...verbatim }) via the new
FieldsNormalizer(ADR-0002). Consumers reading the raw map shape must switch to the
documentedFieldtype; unknown authored keys still pass through verbatim. Seedocs/API.md
§ Fields canonicalisation.
Pull Requests
- #96 — docs(adr): bootstrap ADR practice + ADR-0002 canonical fields open contract
- #97 — feat: fields overview — canonical fields API + /fields page (#95)
Full Changelog: v1.5.1...v1.6.0