oxidecomputer / oxidecomputer/prettier-plugin-asciidoc

Five decision sites no input reaches: printedGap's blank drop, whitespace row A12, three table declines

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

Nobody has claimed this yet.

foundation mechanism:instrument obligation:completeness
Dominant language
TypeScript
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

What this is

Five decision sites the Sep 7 ablation study (category-collapse.md) could not reach with any input, over 1,876 real documents and the test suite: printedGap's blank-drop arm (src/print/list.ts:838-848; its own test comment says "the recorded gap is already empty here"), whitespace fact row A12 (src/whitespace-fact.ts:429-431, an anchor: reftext holding a multi-space run), and three TableDecline members (unterminated table-layout.ts:288-299, attribute-reference :556-580, and one more the study names) that fire on none of 271 tables and have no test row. Same shape as #260: a branch nothing reaches.

The change

For each: construct a reaching input and pin it, or delete the arm and its census entry (the TableDecline census pins the member set, so a deletion is a census edit). The study's per-site notes are the starting point.

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 the per-site notes in category-collapse.md, then inspect src/print/list.ts:838-848, src/whitespace-fact.ts:429-431, and the TableDecline members in table-layout.ts:288-299 and :556-580. Determine the missing third TableDecline site from the study and check the related tests and census entry. Done means each site has a pinned reaching input, or its arm and census entry are removed, with the test suite passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
testing, tooling
Issue type
Refactor
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.