mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-19 06:35:44 +01:00
Answer product-owner round 1: the README says a parse's path points into the document the call returns
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user