larvit/adf-codec
3
0
Fork 0
mirror of https://github.com/larvit/adf-codec.git synced 2026-11-12 11:48:29 +01:00
Code Activity

Answer prose round 1: 0 🔴, 6 🟡 (0 misread); reword the spanning comments, spec and changelog entry

Browse Source
This commit is contained in:
Lilleman auf Larv
2026-10-31 03:56:44 +01:00
committed by Lillem4n
parent f77b9f91a1
commit b2b124277a
4 changed files with 17 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/flavour.md
+6 -4
View File
@@ -564,10 +564,12 @@ marks array in order, outermost first: `_!adf:underline[x]_` gives marks `[em, u
the array, not a set — and opens each spelling once over the longest run of adjacent inline nodes
carrying an identical mark, attributes included, at that depth: `attrs: {}` differs from no `attrs`,
and a directive spells it `{attrs=empty}`. A run breaks at every node the emitter carries, so no
emitted carry sits inside a mark spelling. An emphasis or link run also spans the nodes between two
it marks that take no mark of its type, where the line reads back so: `_One\` then `Two_` is one
`em` over two texts and the hard break between, ``**Run `npm ci` first**`` one `strong` around
plain code. `adfToPortableMarkdown` spans hard breaks and code spans the same way.
emitted carry sits inside a mark spelling. An `em`, `strike`, `strong` or `link` run also spans a
node between two of its nodes when that node cannot hold the run's mark. It does so only where the
spanned line reads back to the same marks; otherwise the run breaks there. So `_One\` then `Two_`
is one `em` run over two texts, the hard break between them unmarked, and
``**Run `npm ci` first**`` is one `strong` run around unmarked code. `adfToPortableMarkdown` spans
hard breaks and code spans the same way.
An inline node whose marks no nesting spells — a node holding a mark Atlassian's schema withholds
from it, a mark type the first list above does not hold, an attrs key its spelling does not list, a value that is not the