mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-12 11:48:29 +01:00
Answer product-owner round 1: the README's read-back cell states the split, and the changelog and decision word it exactly
This commit is contained in:
+2
-2
@@ -52,8 +52,8 @@
|
||||
brackets literal text, where `0.1.0` split the outer link around it; see `MIGRATION.md`.
|
||||
- Add `adfToPortableMarkdown` and `portableMarkdownToAdf`, a lossy pair converting ADF to and from
|
||||
markdown GitHub, GitLab and Obsidian render: alerts, callouts, task lists, `==highlights==` and
|
||||
pipe tables. A task item holds only paragraphs, as Atlassian's schema requires: from its first
|
||||
other block, such as an image or a code block, the rest of the item stands after the task list.
|
||||
pipe tables. A task item holds only paragraphs: from its first other block, such as an image or
|
||||
a code block, the rest of the item stands after the task list.
|
||||
- Spell `rule`'s `color`, `style` and `weight`, `layoutSection`'s `columnRuleStyle` and a link's
|
||||
`collection`, `id` and `occurrenceKey` directly where they rode the opaque carry.
|
||||
- Fix an image inside another image's description: it flattens into the alt text, where it was
|
||||
|
||||
@@ -127,7 +127,7 @@ saving what this pair read replaces mentions, attachments and macros with text.
|
||||
| --- | --- | --- |
|
||||
| `panel` | a GitHub alert, `> [!WARNING]`: info `NOTE`, note `IMPORTANT`, tip and success `TIP`, warning `WARNING`, error `CAUTION`, custom `NOTE` | `NOTE` info, `IMPORTANT` note, `TIP` tip, `WARNING` warning, `CAUTION` error, and Obsidian's: hint tip; success, check, done success; attention warning; danger, failure, fail, missing, bug, error error; any other word info — in any case; the rest of the marker's line is the first paragraph |
|
||||
| `expand`, `nestedExpand` | Obsidian's folded callout, `> [!NOTE]- Title` | `-` or `+` after any word, the rest of the marker's line the title; a link reads `text (target)`, or its text alone where the text is the target with or without `mailto:`; an expand inside an expand is a `nestedExpand` |
|
||||
| `taskList` | `- [x] Done`, `- [ ] Todo`; an item keeps its paragraphs up to its first other block, which stands with the rest of the item after the list, the list resuming at the next task | a bullet list whose every item is so marked, `[X]` too; an item's blocks as written |
|
||||
| `taskList` | `- [x] Done`, `- [ ] Todo`; from an item's first block other than a paragraph, the rest of the item after the list, which resumes at the next task | a bullet list whose every item is so marked, `[X]` too; from an item's first block other than a paragraph, the rest of the item after the list, which resumes at the next task |
|
||||
| `backgroundColor` | `==text==` | `==text==` on one line, the text touching both delimiters, bounded outside by whitespace, punctuation or a line edge, or touching a Han, Hangul, Hiragana, Katakana, Thai, Lao, Khmer or Myanmar character on either side, in the editor's default highlight `#f8e6a0` |
|
||||
| `table` | a pipe table: the first row its header, a cell's blocks on one line, a span kept under its header by empty cells | — |
|
||||
| `decisionList` | a bullet list | — |
|
||||
|
||||
+5
-5
@@ -254,11 +254,11 @@ markdown pasted twice into one document repeats its ids: determinism wins over t
|
||||
|
||||
In `portableMarkdownToAdf` and `adfToPortableMarkdown`, a task item keeps its paragraphs up to its
|
||||
first other block. That block, the item's blocks after it and the task lists nested in the item
|
||||
stand after the task list, which resumes at the next task. The panel of two bots, two LLM
|
||||
pipelines, a support agent, a product manager and an engineer, shown an image, a code block and a
|
||||
nested bullet list in a task item, picked this over turning those blocks into text inside the item
|
||||
(1 of 7) and over a plain bullet list keeping the markers as text (none): every reader wanted the
|
||||
checkboxes, and six wanted the blocks in their own form.
|
||||
after that block stand after the task list, which resumes at the next task. The panel of two bots,
|
||||
two LLM pipelines, a support agent, a product manager and an engineer, shown an image, a code block
|
||||
and a nested bullet list in a task item, picked this over turning those blocks into text inside
|
||||
the item (1 of 7) and over a plain bullet list keeping the markers as text (none): every reader
|
||||
wanted the checkboxes, and six wanted the blocks in their own form.
|
||||
|
||||
## A callout title keeps its link targets
|
||||
|
||||
|
||||
Reference in New Issue
Block a user