mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-19 06:35:44 +01:00
Answer prose round 1: 1 🔴, 13 🟡 (1 misread); correct the migration recipe, tighten the specs and item 168's detail
This commit is contained in:
+9
-6
@@ -27,12 +27,15 @@ the error's `path` naming the card, since Atlassian's schema gives a card no lin
|
||||
`link` mark from that card before you write it with `0.3.0`; to keep the link's target, put the
|
||||
link on a `text` node beside the card.
|
||||
|
||||
`0.3.0` refuses, as `unsupported-node-shape`, a block or non-text inline node holding `text`, and a
|
||||
leaf block or non-text inline node holding non-empty `content`. Atlassian's schema gives no node
|
||||
those. `adfToHtml` and `adfToPortableMarkdown` wrote such a node in `0.2.0`, and `adfToLosslessMarkdown`
|
||||
wrote one inside a carried node; all three now refuse it, and `losslessMarkdownToAdf` and `htmlToAdf`
|
||||
refuse a stored carry holding one. Read a stored document with `0.2.0`, remove what the error's
|
||||
`path` names and write it with `0.3.0`, once.
|
||||
`0.3.0` refuses, as `unsupported-node-shape`, a known block holding `text`, a known non-text inline
|
||||
node holding `text` or non-empty `content`, and a known block that takes no content, such as `rule`,
|
||||
holding non-empty `content`. Atlassian's schema allows none of these. `adfToPortableMarkdown` wrote
|
||||
such a node in `0.2.0`, and `adfToLosslessMarkdown` wrote one inside a carried node. Both now refuse
|
||||
it, and `losslessMarkdownToAdf` refuses stored markdown whose carry holds one.
|
||||
|
||||
Read such stored markdown with `0.2.0`, then write the document with `0.3.0`. Each refusal names one
|
||||
wrong key, `text` or `content`, on the node the error's `path` names, and a call reports only the
|
||||
first: delete that key and write again until the call succeeds.
|
||||
|
||||
## From `0.1.0` to `0.2.0`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user