Skip to content

docs(intent): unknown keys are errors, never silent - #187

Merged
delchev merged 1 commit into
masterfrom
docs/intent-unknown-keys
Aug 15, 2026
Merged

docs(intent): unknown keys are errors, never silent#187
delchev merged 1 commit into
masterfrom
docs/intent-unknown-keys

Conversation

@delchev

@delchev delchev commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Documents eclipse-dirigible/dirigible#6748 (closes eclipse-dirigible/dirigible#6541).

A key the intent does not declare — an invented one, or a case slip (Required: for required:) — now fails validation instead of being dropped by the typed mapping. intent-file.md gains:

  • Unknown keys are errors, never silent under Authoring rules: why the old silence was the worst outcome (parse 200 → publish 200, with the authored promise absent at runtime), the real message, and which two shapes are checked — the DSL's own keys and a seed row's keys.
  • A seeds paragraph: row keys are the entity's field and to-one relation names (or the stage marker), matched exactly, with the real message and what a dropped NOT NULL foreign key costs (the import skips every row).

Built locally with npm run docs:build; anchors resolve.

A key the intent does not declare - an invented one, or a case slip - fails
validation instead of being dropped by the typed mapping, so the Intent Editor,
the Builder and POST /parse all name it, where it sits and the nearest declared
name. Documents both halves: the DSL's own keys, and a seed row's keys (the
entity's field and to-one relation names), with the real messages and what the
old silence cost - a dropped NOT NULL foreign key makes the import skip every
row.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

intent: unknown seed row key is silently dropped - should be a generation error

1 participant