mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-19 06:35:44 +01:00
Answer prose round 1: the README says which refusal differs between engines, items 106 and 107 read one idea a sentence, and two test titles and a comment read on one pass
This commit is contained in:
+3
-3
@@ -463,9 +463,9 @@ handles one cause alike whichever node, attribute or direction raised it.
|
||||
emitting — no document holds one, so no round-trip crosses them (2026-09-23).
|
||||
- A document whose markdown would be longer than the longest string or array the JavaScript engine
|
||||
builds is `unsupported-node-shape` at the document's path, in either writer: the document does
|
||||
not convert, and the bound is the engine's own. A carried node reaches it on about 1 MB of
|
||||
deeply nested JSON, since the block carry indents two spaces a level; `todo.md` item 107 spells
|
||||
it in a length linear in its JSON (2026-10-11).
|
||||
not convert, and no spelling in the input causes the bound (§The code list). A carried node
|
||||
passes it on about 1 MB of deeply nested JSON, since the block carry indents two spaces a level;
|
||||
`todo.md` item 107 respells the carry in a length linear in its JSON (2026-10-11).
|
||||
- The markdown readers and `htmlToAdf` refuse a value that is not a string as `not-a-string`, at
|
||||
position `{ line: 1, offset: 0 }` with an empty path: no existing code reads true of it, and
|
||||
`not-an-adf-document` names the emitters' input (2026-10-05).
|
||||
|
||||
Reference in New Issue
Block a user