mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-18 22:25:44 +01:00
Answer architecture round 1: the guard refuses only the measured overflow errors, the README keeps such a document read-only, and items 106 and 107 take the heap and the carry's indentation
This commit is contained in:
+3
-1
@@ -463,7 +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 runs past the longest string the JavaScript engine holds 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 (2026-10-11).
|
||||
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).
|
||||
- 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