From 97bd801c58209d716fee541664d905e0a029caae Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Sat, 31 Oct 2026 02:50:23 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20prose=20round=201:=201=20=F0=9F=94=B4,?= =?UTF-8?q?=206=20=F0=9F=9F=A1=20(0=20misread);=20reword=20the=20border=20?= =?UTF-8?q?entries,=20move=20the=20README=20row?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 4 ++-- docs/decisions.md | 6 +++--- spec/flavour.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index fed0d3b..7776433 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -30,8 +30,8 @@ around only code spans is `unsupported-node-shape`. `adfToLosslessMarkdown` writes code text holding another mark as `!adf:carry{json="…"}`, and `adfToPortableMarkdown` drops that mark. - **Breaking:** `losslessMarkdownToAdf` gives text no `border` mark, as Atlassian's schema requires: - `!adf:border[x]{color="#091e42" size=2}` is `unsupported-node-shape`, and `border` marks a - `mediaInline` alone. `adfToLosslessMarkdown` writes text holding `border` as `!adf:carry{json="…"}`. + `!adf:border[x]{color="#091e42" size=2}` is `unsupported-node-shape`, and only a + `mediaInline` takes `border`. `adfToLosslessMarkdown` writes text holding `border` as `!adf:carry{json="…"}`. `MIGRATION.md` says how to convert stored markdown. - Every reader keeps the URL and title of an image inside a link's text, where it dropped them: after the link comes `(image)`, which links to the image, so diff --git a/docs/decisions.md b/docs/decisions.md index 27a2d0b..84c443a 100644 --- a/docs/decisions.md +++ b/docs/decisions.md @@ -285,10 +285,10 @@ content (`README.md` `## Goals`, Goal 7). each. Goals 1, 4 and 6. Valid while Atlassian's schema withholds marks from inline nodes. Extended to code text under this rule, without a panel, 2026-10-14; retitled by the maintainer the same day, keeping the directive-mark refusal the old title held. Extended to `border` on text, which the -schema withholds from formatted text, 2026-10-31, without a panel. +schema withholds from text, 2026-10-31, without a panel. -A mark spelling skips a node that takes none of its type, code text included, which takes only -`code`, `link` and `annotation`, and text of any kind, which takes no `border`. So +A mark spelling skips a node that takes none of its type. Code text takes only `code`, `link` and +`annotation`, and no text takes `border`. So `**Ping !adf:mention[@A]{id=x} now**` reads as bold text around a plain mention, and ``**`npm ci`**`` as plain code. A directive mark wrapping only nodes that take none of its type is `unsupported-node-shape` in `losslessMarkdownToAdf`. So is a link whose text holds something diff --git a/spec/flavour.md b/spec/flavour.md index fe2d854..a1474bd 100644 --- a/spec/flavour.md +++ b/spec/flavour.md @@ -556,7 +556,7 @@ A block's `marks` key also holds these, which no inline spelling wraps: - `indentation` — Attributes: `level` (number, 1–6). A spelling adds its mark to every inline node it wraps that Atlassian's schema gives the mark. Text -takes every mark but `border`, and text marked `code` takes no other spelled mark but `link`: +takes every mark but `border`. Text marked `code` takes no other spelled mark but `link`: ``**`npm ci`**`` reads as plain code. Of the marks a spelling makes, `date`, `emoji`, `hardBreak`, `inlineCard`, `mention` and `status` take none, and `mediaInline` takes only `border` and `link`. Nesting is the marks array in order, outermost first: `_!adf:underline[x]_` gives marks `[em, underline]`,