From 29c519ac58bc4087a450e629db51da9d5f9494ee Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Tue, 17 Nov 2026 00:02:35 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20prose=20round=201:=200=20=F0=9F=94=B4,?= =?UTF-8?q?=203=20=F0=9F=9F=A1=20(0=20misread);=20say=20once=20that=20ment?= =?UTF-8?q?ions=20and=20localId-bearing=20nodes=20ride=20the=20carry?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/decisions.md | 11 +++++------ todo.md | 2 +- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/decisions.md b/docs/decisions.md index 6440a51..81bbbb0 100644 --- a/docs/decisions.md +++ b/docs/decisions.md @@ -1473,7 +1473,7 @@ call with `{ lossy: true }`, and over `adfToPortableWiki`, which sounds like the reader who hasn't seen the trap. The reader is `jiraWikiToAdf`. The maintainer picked it on 2026-11-17, after the readers split four -to three between it and `jiraWikiMarkupToAdf`, short of the five of seven that settle it +to three between it and `jiraWikiMarkupToAdf`, short of the five of seven that settle a name (`AGENTS.md` §7). ## Jira wiki markup spellings the help leaves open are a writer panel's picks @@ -1495,20 +1495,19 @@ lines, before they wrote their own; the last four did not. ## A plain wiki spelling stands for the attributes Jira's editor writes, and any other attribute rides the carry -2026-11-16, the implementer of the wiki spec; the maintainer confirmed the carry of `localId` and a -mention's `text` on 2026-11-17. Goals 1, 6 and 11. +2026-11-16, the implementer of the wiki spec; the maintainer confirmed on 2026-11-17 that `localId` and a +mention's `text` ride the carry. Goals 1, 6 and 11. Valid while Jira's editor writes these defaults. Real Jira documents hold attributes that wiki markup can't spell: `order` 1 on every ordered list, `accessLevel` `""` on every mention, `isNumberColumnEnabled` `false` and `layout` `default` on every table, `layout` `center` on `mediaSingle`, `language` `""` on a code block. A plain spelling -stands for exactly that one value and the reader writes it, so a Jira-authored document writes as +stands for exactly that one value and the reader writes it, so most of a Jira-authored document writes as wiki markup, not as JSON. Any other value, an absent attribute, `localId` and a mention's `text` among them, rides the carry, so the plain spelling reads back deep-equal: the lossless writer keeps each attribute (`docs/decisions.md` §Ids stay site-local), and the lossy writer drops it. `[~name]` reads as text, not as a mention with `id` `name`, since Jira Cloud names a user by account id and the writer would otherwise write a different account back. -The lossless writer drops no attribute, a mention's `text` and any `localId` included, since it -would then no longer be lossless. A real document holding them writes those nodes as `{adf}` JSON. +In a real Jira document, each mention and each node holding a `localId` therefore writes as `{adf}` JSON. ## `htmlToAdf` reads any HTML, with no option and no second call diff --git a/todo.md b/todo.md index f97c586..ef11f7d 100644 --- a/todo.md +++ b/todo.md @@ -61,7 +61,7 @@ lossless writer does, except where that writer would use the `{adf}` macro. A hand-written reader, as `htmlToAdf` is. Ships with the property that what the lossless writer of item 193 writes reads back deep-equal, and with refusals whose codes come from the closed list. -The reader is `jiraWikiToAdf`, the maintainer's pick (`docs/decisions.md` §Jira wiki markup's writers +The reader is `jiraWikiToAdf` (`docs/decisions.md` §Jira wiki markup's writers are `adfToLosslessJiraWiki` and `adfToLossyJiraWiki`, two calls with no option). ### 196. Document the wiki calls in the README, with a row comparing them with Atlassian's `WikiMarkupTransformer`.