oxidecomputer / oxidecomputer/prettier-plugin-asciidoc
A paragraph after a nested list with a blank run behind its + leaves the outer item
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
What happens
A nested list whose leading gap carries a blank run behind its +, followed by an indented sibling marker and then a paragraph, loses the paragraph out of the outer item:
* a
** b
+
** z
para
Both Asciidoctor Ruby 2.0.26 and @asciidoctor/core 4.0.11 put para inside the outer item a; the plugin prints it outside (a document-level paragraph). Fifteen of a 540-document two-program probe fail this way (five heads x nine runs x twelve tails; 359 binding); identical on main and under both the withholding and the truncating spelling of the item's leading gap (the #184 change), so no leading-gap spelling reaches it. The body is seven lines, outside the depth-5 list-shape product.
Mechanism
Where the paragraph after the nested list lands, not what the gap spells: the reader closes the outer item at the nested list's end and the following paragraph is not attached, where the reference's list-continuation state still attaches it. Stated at the site in separatorBefore's domain paragraph (src/print/list.ts, the #184 change).
Related
#184 (the leading gap), #121, #161 (the depth-5 product's alphabet).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/print/list.ts at separatorBefore's domain paragraph and trace how the reader closes the outer item after the nested list. Reproduce the seven-line example and run the two-program probe; done means the following paragraph remains inside the outer item, matching Asciidoctor Ruby and @asciidoctor/core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100