oxidecomputer / oxidecomputer/prettier-plugin-asciidoc
A folded comment carrying a dlist separator word keeps its line and its render loss
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Residual of #105 after its fix (2026-09-03), deliberately left, 27
grid rows, all byte-identical to main. A content comment in a dlist
description whose text carries a :: or ;; separator word (// x:: y)
is NOT folded into the reflowable run: folding it puts a term word
where the printer's dlist first-line hazard breaks the line, and the
second read fabricates a
render loss). So the comment keeps its own line outside the
description, which is #105's original loss narrowed to this one
payload shape. The guard is holdsDescriptionListSeparator
(src/parse/lines/classify.ts) asked by the paragraph reader's fold.
A proper fix needs the packer to reason about whole OUTPUT lines
(the same class as issue #109); until then the boundary row x::y
(separator inside a word, still folds) pins the edge.
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/parse/lines/classify.ts with holdsDescriptionListSeparator, then trace the paragraph reader's fold and the packer behavior described alongside issue #109. Verify the boundary case x::y still folds while a dlist-description comment containing a separator word stays on its own line and does not fabricate a
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
- Mostly clear
- Newbie friendliness
- 45/100