Pin the link mark's two error codes, and correct what the unspellable corpus holds
CI / gate (push) Successful in 5s
CI / gate (push) Successful in 5s
This commit is contained in:
@@ -90,6 +90,8 @@ test('refuses a link attribute no markdown spelling holds', () => {
|
|||||||
code(adfToMarkdown(document(paragraph({ marks: [{ attrs: { href: 'https://example.com/', id: 'x' }, type: 'link' }], text: 't', type: 'text' })))),
|
code(adfToMarkdown(document(paragraph({ marks: [{ attrs: { href: 'https://example.com/', id: 'x' }, type: 'link' }], text: 't', type: 'text' })))),
|
||||||
'unspellable-mark',
|
'unspellable-mark',
|
||||||
)
|
)
|
||||||
|
assert.equal(code(adfToMarkdown(document(paragraph({ marks: [{ attrs: { href: 4 }, type: 'link' }], text: 't', type: 'text' })))), 'unspellable-mark')
|
||||||
|
assert.equal(code(adfToMarkdown(document(paragraph({ marks: [{ type: 'link' }], text: 't', type: 'text' })))), 'unsupported-node-shape')
|
||||||
})
|
})
|
||||||
|
|
||||||
test('refuses a mark the canonical spellings cannot nest', () => {
|
test('refuses a mark the canonical spellings cannot nest', () => {
|
||||||
|
|||||||
@@ -110,7 +110,10 @@ detail is settled at its own milestone.
|
|||||||
arg slot holding no bare token, marks no nesting spells — where the emitter still refuses,
|
arg slot holding no bare token, marks no nesting spells — where the emitter still refuses,
|
||||||
which leaves the refusals a container's own spelling owns. The carry spells
|
which leaves the refusals a container's own spelling owns. The carry spells
|
||||||
`escaping: 'none'`, which is what makes `tryPipeCell` refuse the pipe form for a carry
|
`escaping: 'none'`, which is what makes `tryPipeCell` refuse the pipe form for a carry
|
||||||
whose JSON holds a pipe.
|
whose JSON holds a pipe. The flanking trigger 2e2 added to that list is the odd one out:
|
||||||
|
`unspellableMark` finds it after assembly and names a mark type against the line's path,
|
||||||
|
so the failing run needs identifying before the carry can replace the refusal
|
||||||
|
`corpus/unspellable/mark-inside-word` pins.
|
||||||
- [ ] **2e5 — Combined documents and the collision property.** Documents combining nodes rather
|
- [ ] **2e5 — Combined documents and the collision property.** Documents combining nodes rather
|
||||||
than isolating one, and the gate's collision property: no two corpus documents may emit
|
than isolating one, and the gate's collision property: no two corpus documents may emit
|
||||||
the same bytes — one spelling for two documents is a round-trip break no parser can undo,
|
the same bytes — one spelling for two documents is a round-trip break no parser can undo,
|
||||||
@@ -169,8 +172,8 @@ detail is settled at its own milestone.
|
|||||||
markdown, the payloads supplied by the maintainer.
|
markdown, the payloads supplied by the maintainer.
|
||||||
- [ ] **5 — Release pipeline, ship `0.1.0`.** Publish-on-version-change (§9), `NPM_TOKEN` secret,
|
- [ ] **5 — Release pipeline, ship `0.1.0`.** Publish-on-version-change (§9), `NPM_TOKEN` secret,
|
||||||
the repo made public first (§6). The `ConvertErrorCode` freeze (§8) is checkable here: every
|
the repo made public first (§6). The `ConvertErrorCode` freeze (§8) is checkable here: every
|
||||||
`corpus/unspellable/` document is one of 1d's decisions, so the directory empties as they land
|
`corpus/unspellable/` document is a decision or a deferred trigger this file names, so the
|
||||||
and whatever survives is permanent. `0.1.0` is the markdown round-trip: both markdown
|
directory empties as they land and whatever survives is permanent. `0.1.0` is the markdown round-trip: both markdown
|
||||||
directions, the types, `isAdfDocument`. The build lands here: a build tsconfig emitting JS
|
directions, the types, `isAdfDocument`. The build lands here: a build tsconfig emitting JS
|
||||||
and `.d.ts` to `dist/` (the dev config's `allowImportingTsExtensions` forces `noEmit`, so
|
and `.d.ts` to `dist/` (the dev config's `allowImportingTsExtensions` forces `noEmit`, so
|
||||||
the build config needs `rewriteRelativeImportExtensions`), plus `exports`/`files` in
|
the build config needs `rewriteRelativeImportExtensions`), plus `exports`/`files` in
|
||||||
|
|||||||
Reference in New Issue
Block a user