NogginErrorData
The structured payload attached to NogginError.data. Each code carries a known set of fields; hosts pattern-match on code and read the fields they need. Extra fields are non-breaking.
Structured payload attached to NogginError.data. Each error code carries a known set of fields (best-effort — additional fields are non-breaking). Hosts that render user-facing strings key off code and read fields from here.
Engine message is a short host-neutral fact for logs and fallback. Hosts SHOULD prefer their own catalog (see e.g. cli/error-messages.mjs, @noggin/ui/errors) over showing message directly.
Common fields: - verb — the verb name where the error originated (e.g. 'move'). - path — absolute path of the item involved. - title — the item's title at the time of the error. - detail — free-form supplementary text (e.g. underlying I/O message).
Code-specific fields (illustrative; treat as additive): - open-descendants: { verb, path, title, openCount } - has-descendants: { verb, path, title, descendantCount } - cycle: { verb, path, title, placementKind } - path-not-found: { path, detail } - no-provider: { scheme?, location } - placement-invalid: { verb, kind } - invalid-document: { key?, parentKey?, active? }
Indexable
[extra: string]: unknown