Skip to content

docs: restore section template comments in ndarray/base/diagonal and ndarray/last#11903

Draft
Planeshifter wants to merge 2 commits intodevelopfrom
philipp/fix-commit-review-2026-05-03
Draft

docs: restore section template comments in ndarray/base/diagonal and ndarray/last#11903
Planeshifter wants to merge 2 commits intodevelopfrom
philipp/fix-commit-review-2026-05-03

Conversation

@Planeshifter
Copy link
Copy Markdown
Member

Description

Follow-up fixes for commits merged to develop between c2b92b4 (2026-05-02 18:43:33 -0700) and 186eaa37 (2026-05-03 04:42:10 -0700).

This pull request:

  • ndarray/base/diagonal: Fixes ndarray/base/diagonal README (632bef35) which omitted the five boilerplate section-separator HTML comments required before each top-level <section>, present in sibling packages such as ndarray/base/rot90.
  • ndarray/last: Fix truncated intro-section template comment in lib/node_modules/@stdlib/ndarray/last/README.md introduced in 9e8bb89b; restores the canonical wording (...intro \section` element and another before the `/section` close.`) consistent with all sibling packages.

Related Issues

No.

Questions

No.

Other

Validation audit of the 18 commits merged to develop in the past 24 hours (range c2b92b4..186eaa37):

  • Checked: stdlib code style compliance against docs/style-guides; objective bug scan over the union diff and the introduced code in the new packages (blas/base/ndarray/cswap, blas/base/ndarray/zswap, ndarray/base/diagonal, ndarray/base/reverse-dimensions, ndarray/last); follow-up fixes in the stats/strided/dpcorr chain.
  • Excluded: subjective concerns, "could be" issues, anything requiring out-of-window changes, anything already addressed by the in-window bench: refactor to use string interpolation in utils, style: resolve lint error in ndarray/fancy, and chore: propagate fixes to sibling packages commits.
  • Result: only the two README template-comment fixes above survived multi-agent corroboration and re-verification against the diff and reference siblings.

Checklist

AI Assistance

  • Yes
  • No

If you answered "yes" above, how did you use AI assistance?

  • Code generation (e.g., when writing an implementation or fixing a bug)
  • Test/benchmark generation
  • Documentation (including examples)
  • Research and understanding

Disclosure

This PR was authored by Claude Code as part of an automated review of commits merged to develop in the past 24 hours. Style-compliance and bug-scan agents inspected the union diff; only findings corroborated by re-reading the diff against reference siblings were applied.


@stdlib-js/reviewers


Generated by Claude Code

@stdlib-bot
Copy link
Copy Markdown
Contributor

Coverage Report

Package Statements Branches Functions Lines
ndarray/base/diagonal $\color{green}188/188$
$\color{green}+100.00%$
$\color{green}22/22$
$\color{green}+100.00%$
$\color{green}1/1$
$\color{green}+100.00%$
$\color{green}188/188$
$\color{green}+100.00%$
ndarray/last $\color{green}249/249$
$\color{green}+100.00%$
$\color{green}27/27$
$\color{green}+100.00%$
$\color{green}2/2$
$\color{green}+100.00%$
$\color{green}249/249$
$\color{green}+100.00%$

The above coverage report was generated for the changes in this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants