From be3ac4af22a1e3f74821a23a54c3777b85da8e5a Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Sun, 11 Oct 2026 11:59:43 +0200 Subject: [PATCH] Answer product-owner round 1: the README says a parse's path points into the document the call returns --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index dafa6fa..8d56d6c 100644 --- a/README.md +++ b/README.md @@ -174,7 +174,8 @@ 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. +being the document itself. A parse's path points into the document the call returns once the +refusal is fixed. 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