3
0
mirror of https://github.com/larvit/adf-codec.git synced 2026-11-18 22:25:44 +01:00

Answer architecture round 1: 0 🔴, 2 🟡; the slot's line ending is a value the slot does not take, and its message offers the space again

This commit is contained in:
2026-10-14 00:05:02 +02:00
committed by Lillem4n
parent ed401ec7b6
commit 5cd07cafec
5 changed files with 7 additions and 7 deletions
+3 -3
View File
@@ -437,9 +437,9 @@ handles one cause alike whichever node, attribute or direction raised it.
- A code names the cause; where one cause recurs across node types, across one mark's attributes
or across directions, one code covers them all and `path` and `message` say which —
`unsupported-nesting-depth` is the 500-level guard whichever direction hits it.
A line ending or a null character an inline directive's content slot spells in input is
`unsupported-node-shape`, as both take one fix, the carry; the emitter carries such a node
(2026-10-14).
A line ending or a null character in an inline directive's content slot is a value the slot does
not take, so `unsupported-node-shape` as below, `message` naming the character; the emitter
carries such a node (2026-10-14).
- A claim code names the spelling claimed, never the node that spelling would have built: a
malformed `!adf:table` is a `malformed-directive`, and an alignment colon a
`malformed-pipe-table` — the flavour's own delimiter row is `-` runs, so the grammar refuses the