oxidecomputer / oxidecomputer/prettier-plugin-asciidoc
A glued-run first line loses the author's break
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
"####\nb c\n" formats to "#### b c\n" (render-unequal): the source's first line is TWO glued atoms (### + #, since ## opens a highlight span), and keepBlockStartBreak breaks before atoms[1] only — restoring the author's break AFTER a glued RUN is a different rule the block-start net does not have. 23 documents in the block-start audit population carry the shape.
Not a regression: render-unequal on every measured revision. No sweep alphabet spells a column-0 paragraph opening on a lone marker-shaped token, so nothing in the suite will notice a regression here beyond the pinned rows; a fix should extend the alphabet or pin the family's boundary members.
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 by tracing keepBlockStartBreak and the block-start audit population, focusing on how atoms[1] handles the two-atom glued run. Review the pinned rows and existing sweep alphabet; done means the author's break is preserved after the glued run and the marker-shaped boundary is covered by an added alphabet case or pinned family member.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100