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

Answer prose round 1: the README drops the parse-path sentence and the comments say what stands in and why

This commit is contained in:
2026-10-11 12:01:26 +02:00
committed by Lillem4n
parent be3ac4af22
commit cc40fb95f2
5 changed files with 7 additions and 8 deletions
+1 -2
View File
@@ -174,8 +174,7 @@ and may change in any release. A parse always names a position, so the three mar
alone; one handler typed on `ConvertError` takes both, which is what the calls between markdown and
HTML hand back. `path` is the node's place from the document root, alternating `'content'` and an
index, so `path.map((step) => '/' + step).join('')` is a JSON Pointer at the node — the empty path
being the document itself. A parse's path points into the document the call returns once the
refusal is fixed.
being the document itself.
A call reports the first refusal in document order and stops, so a document with several surfaces
them one per call. Every refusal is deterministic — there is no I/O anywhere — so a retry returns