top-level annexes do not support explicit numbers
Open
Nobody has claimed this yet.
feature
- Dominant language
- TypeScript
- Stars
- 245
- Forks
- 80
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 2
Description
top-level annexes do not support explicit numbers; if you need this, open a bug on ecmarkup
I need to make a change to Annex B, and I want it to show up as "B", and I don't want to have to add a placeholder for "A".
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
No file or test is named in the issue. Start by tracing how ecmarkup handles top-level annexes, then verify that an annex explicitly numbered B renders as B without an A placeholder while existing numbering behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100