docs: an unrecognised key is an authoring error, never ignored - #23
Open
delchev wants to merge 2 commits into
Open
docs: an unrecognised key is an authoring error, never ignored#23delchev wants to merge 2 commits into
delchev wants to merge 2 commits into
Conversation
Mirrors the specification change: the Unrecognised keys rule in Authoring rules, and the sharpened seed-row rule (a field name, a to-one relation name, or the stage marker - and what accepting anything else silently costs).
Mirrors the specification change: the per-kind rule for a step's args, the list of blocks that are a fixed vocabulary despite being written as a mapping, and a delegate's injected fields: added to the free-form list.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirrors IntentFile/intent-specification#24.
docs/spec/index.md— the Unrecognised keys rule in Authoring rules (with the::: info Normativecontainer), plus the bullet that only declared, case-sensitive keys exist.docs/spec/data.md— the seed-row rule sharpened the same way: a field name, a to-one relation name or thestagemarker, and what accepting anything else silently costs.No new construct, so
reference.mdis unchanged. Built locally withnpm run docs:build; the new#unrecognised-keysanchor and both cross-links resolve in the built HTML.