Repository navigation
docs: fix heading levels - #15939
Merged
Merged
docs: fix heading levels#15939
Conversation
Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
…rray` Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
…ray` Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
Changed `## Notes` to `### Notes` within the C APIs section so the heading nests beneath `## C APIs` alongside `### Usage` (`### Usage` present in 100% of `napi` siblings; `### Notes` used for C API notes in 74 of 82 READMEs stdlib-wide, with the remaining 8 being this and its `napi` siblings). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
Contributor
Coverage Report
The above coverage report was generated for the changes in this PR. |
kgryte
marked this pull request as ready for review
October 12, 2026 00:23
kgryte
approved these changes
Oct 12, 2026
napi/argv-* READMEs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request:
## Notesto### Notesin the C APIs section of eightnapiREADMEs, so the heading nests under## C APIslike the existing### Usagesubsection.Namespace summary.
@stdlib/napihas 53 members and none are autogenerated. Seven structural features were analyzed: file tree,package.jsonkeys,package.jsonscripts/stdlibkeys,manifest.jsonkeys, keywords, README sections, and test/benchmark/example file names. Every feature has a clear majority (at least 75%). The JS sources (lib/main.js,lib/index.js,lib/browser.js) are identical across all 53 packages apart from the package name, so they show no semantic drift.napi/argv-complex128array,napi/argv-complex64array,napi/argv-int32,napi/argv-int64,napi/argv-strided-complex128array,napi/argv-strided-complex64array,napi/argv-uint32,napi/argv-uint64The C API notes heading was at level two, which takes it out of the
## C APIssection.### Usagesits at level three in 100% ofnapisiblings. Across stdlib, READMEs with a C APIs section use### Notesfor C API notes in 74 of 82 cases, and these eight packages are the remaining 8. This is a one-line heading change per package and does not change any content.Related Issues
No.
Questions
No.
Other
Validation. Structural features were extracted for all 53 packages. The JS sources were compared by normalized content hash. Each candidate was then reviewed for structural applicability and checked against tooling and docs that reference it. Remark lint rules check
<section>classes, not heading depth. Nothing links to these#notesanchors, and the JS notes sections are untouched.Deliberately excluded:
napi/argvandnapi/exportlackbinding.gyp,include.gypi,src/,lib/native.js,gypfileanddirectories.src. They are header-only macro packages, so this is intentional.napi/argv-dataview-castlackssrc/main.c. It is header-only (its manifest has an emptysrc), so this is intentional.napi/exportis missing theutilitiesandutilskeywords. This was dropped because it is a low-materiality metadata-only change.Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
This PR was written primarily by Claude Code as part of an automated cross-package drift-detection run.
🤖 Generated with Claude Code
https://claude.ai/code/session_01ChU3fyfvjayXEWk3ZKbg5i
Generated by Claude Code