oxidecomputer / oxidecomputer/prettier-plugin-asciidoc

The reader keeps a foreign marker line verbatim inside an item where the reference reads text; 210 continuation-join confluence pairs read differently on their two sides

Open
#322 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

conformance mechanism:block-reading obligation:confluence
Dominant language
TypeScript
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

What this is

The 210 listContinuationJoin pairs in tests/conformance/confluence-exceptions.ts (63 both-identity, 21 left-identity, 126 both-rewritten) each pair two spellings that our reader reads DIFFERENTLY: one side holds a marker-shaped line the reader keeps verbatim (the verbatim-marker arm in the item scan), the other does not (measured Sep 7 by the #306 lane, confirmed by its review of record on a ten-pair sample of each kind). Under the owner's reading-stability ruling the formatter is right to keep them apart, so no packer mechanism can clear them; the pairs clear only if the reading itself is wrong on one side.

The change

For each of the three kinds, check the reader's verdict on the verbatim-marker side against both programs (parser.rb l.36: a paragraph swallows a following marker-shaped line; the item scan's rule differs). Where our reader diverges, fix the reader (a reader divergence issue per mechanism); where it agrees, the pair is a declared reading difference and leaves the confluence table as a non-goal with the reason at the row.

Related

#195, #306, #313, #57.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with tests/conformance/confluence-exceptions.ts and inspect the 210 listContinuationJoin pairs by kind. Compare the verbatim-marker behavior in the item scan with parser.rb line 36, then run the relevant conformance tests. Done means each pair is either corrected through a reader fix or retained with its declared reading-difference reason.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby, typescript
Domain
testing, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.