mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-18 22:25:44 +01:00
Give the directive grammar, flavours and reader failures one place each
This commit is contained in:
+14
-13
@@ -687,11 +687,11 @@ config gone missing fails the leg instead of falling back to oxlint's own defaul
|
||||
`--deny-warnings`, since a rule from a category this config never names arrives as a warning it
|
||||
exits 0 on.
|
||||
|
||||
## The project ships under the comprehension floor until items 59, 60, 62 and 95 land
|
||||
## The project ships under the comprehension floor until items 62 and 95 land
|
||||
|
||||
2026-10-03, the maintainer; item 95 in place of item 61, 2026-10-09, the maintainer. KISS, a
|
||||
technical principle, and its comprehension floor of 7.
|
||||
Valid while `todo.md` items 59, 60, 62 and 95 are open.
|
||||
Valid while `todo.md` items 62 and 95 are open.
|
||||
|
||||
A four-seat comprehension panel scored the project under the floor of 7. Its scoring run of
|
||||
2026-10-08 is the baseline.
|
||||
@@ -924,14 +924,15 @@ them. A primitive knowing neither ADF nor a format stays at `src/` root. A const
|
||||
what both read where there are two.
|
||||
|
||||
A flavour's own code, both directions included, sits in its own directory: `markdown/portable/`;
|
||||
`todo.md` item 62 moves what still sits in `parse/` and `emit/`. Otherwise each format directory
|
||||
parts into `emit/` (ADF→format) and `parse/` (format→ADF), the rest of it holding what both
|
||||
directions read. A construct's reader lives there beside the regex the emitter escapes against, so
|
||||
the two cannot drift; a reader with no emit counterpart goes in `parse/`, unless it is part of a
|
||||
construct that side already holds — a grammar stays in one file rather than splitting across the
|
||||
seam. A rule both directions must answer alike — whether a list marker interrupts a paragraph — is
|
||||
one function there too, never a copy per direction, however conservative the copy would be. Where
|
||||
the rule is the emitter's own choice, input consults it rather than restating it, and that is the
|
||||
only value import `parse/` takes from `emit/` — `commonMarkSpelling` and `openingLinkTakesDirective`
|
||||
— so no fixture the emitter writes can be refused, and a spelling the emitter refuses gives its own
|
||||
error rather than a second name for it.
|
||||
`todo.md` item 62 moves what still sits in `parse/` and `emit/`. The directive grammar likewise
|
||||
sits in `markdown/directive/`. Otherwise each format directory parts into `emit/` (ADF→format) and
|
||||
`parse/` (format→ADF), the rest of it holding what both directions read. A construct's reader lives
|
||||
there beside the regex the emitter escapes against, so the two cannot drift; a reader with no emit
|
||||
counterpart goes in `parse/`, unless it is part of a construct that side already holds — a grammar
|
||||
stays in one file rather than splitting across the seam. A rule both directions must answer alike —
|
||||
whether a list marker interrupts a paragraph — is one function there too, never a copy per
|
||||
direction, however conservative the copy would be. Where the rule is the emitter's own choice, input
|
||||
consults it rather than restating it, and that is the only import `parse/` takes from `emit/`,
|
||||
through `emit/spelling-questions.ts`, which names `commonMarkSpelling` and
|
||||
`openingLinkTakesDirective` and which a test holds — so no fixture the emitter writes can be
|
||||
refused, and a spelling the emitter refuses gives its own error rather than a second name for it.
|
||||
|
||||
Reference in New Issue
Block a user