Drop hardcoded section numbers from js_dsl example headings
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- zig
- Domain
- documentation
Research direction
Review the section headings in examples/js_dsl/mod.zig and examples/js_dsl/mod.test.ts. Remove each Section N: prefix while preserving the descriptive titles and ==== rule lines. Done means both files use unnumbered headings consistently; no test changes are expected.
Written by the indexing model from the issue text.
Description
examples/js_dsl/mod.zig and mod.test.ts label their sections with hardcoded numbers:
// ============================================================================
// Section 16: Static Class Fields
// ============================================================================
The numbering has already rotted — mod.zig jumps from 11 to 13 and from 13 to 15, so sections 12 and 14 were removed at some point without renumbering. The numbers carry no information the descriptive title doesn't already give, and they force churn (or drift) whenever a section is added or removed.
Raised in review on #76, where the new section was left unnumbered (// Async Tasks). That leaves the file inconsistent, so the remaining headings should follow.
Scope: strip the Section N: prefix from the remaining headings in examples/js_dsl/mod.zig and examples/js_dsl/mod.test.ts, keeping the descriptive titles and the ==== rule lines. Comment-only; no test changes expected.
- Dominant language
- Zig
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from ChainSafe/zapi
-
Type: Maintenance
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
clearer errors Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
certification
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
bisq-network/support#2181 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
tutorial updates Open
Difficulty 1/5 Under an hour Newbie friendliness 80/100
sveltejs/svelte.dev#2241 ·