Merged
Conversation
…ventions Added missing `<section class="notes">` placeholder (present in 96% of siblings) and missing `<section class="references">` placeholder (present in 81% of siblings).
…ntions Added missing `<section class="references">` placeholder (present in 81% of siblings).
…e conventions Added missing `<section class="references">` placeholder (present in 81% of siblings).
…nventions Added missing `<section class="references">` placeholder (present in 81% of siblings).
…ventions Added missing `<section class="references">` placeholder (present in 81% of siblings).
Contributor
Coverage Report
The above coverage report was generated for the changes in this PR. |
array/base/assert with namespace conventions
kgryte
approved these changes
May 2, 2026
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
Aligning outliers in
array/base/assertwith namespace majority patterns (random namespace pick, seed20260501).Namespace summary
array/base/assertpackage.jsonshape, README section markers, test/benchmark/example file namingpackage.jsonkeys (18 keys in 26/26), README<section class="intro|usage|examples|links|related">(26/26), README<section class="notes">(25/26 = 96%), README<section class="references">(21/26 = 81%),@returnsJSDoc tag type{boolean}(26/26),hasExample(26/26), validation prologue empty (26/26), error constructionnone(26/26)__stdlib__package.jsonkey (14/26 = 54%),## Notesmarkdown heading (9/26 = 35%), public signature shape (multiple groups, all <50% — semantic difference, not drift), benchmark filename (benchmark.jsvsbenchmark.length.js— reflects whether the function walks an array)Outliers corrected
is-accessor-arrayAdds empty
<section class="notes">and<section class="references">placeholders to align with namespace siblings, where 96% (25/26) carry a notes section and 81% (21/26) carry a references section. Both sections are present in the overwhelming majority ofarray/base/assertpackages and their absence here was an outlier.is-booleanarrayAdds empty
<section class="references">placeholder to align with 81% ofarray/base/assertnamespace siblings. Maintains structural consistency across the namespace.is-complex-typed-arrayAdds an empty
<section class="references">placeholder to align with 81% ofarray/base/assertsiblings. Brings the package into conformance with the dominant documentation pattern across the namespace.is-complex128arrayAdds an empty
<section class="references">placeholder to align with the 81% ofarray/base/assertsiblings that include this section. Keeps the package consistent with namespace conventions.is-complex64arrayAdds empty
<section class="references">placeholder to align with 81% ofarray/base/assertsiblings. Ensures namespace consistency without altering package behavior.Related Issues
None.
Questions
None.
Other
Validation
What was checked:
package.jsonkeys, README HTML section markers, test/benchmark/example file names)confirmed-driftWhat was deliberately excluded:
(value),(x, y),(x, y, maxULP),(from, to),()-with-factory) reflect genuine semantic differences and have no clear majoritybenchmark.js(constant-time predicates) vsbenchmark.length.js(array-walking predicates) reflects function complexity, not drift__stdlib__package.jsonkey — 14/26 = 54%, below the 75% thresholdChecklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
This PR was authored by Claude Code as part of an automated cross-package API drift detection routine: extract structural and semantic features from every package in a randomly selected namespace, compute the majority pattern for each feature at a 75% threshold, validate findings via review agents, and apply mechanical corrections to outliers. Each correction in this PR was independently verified to be a structural placeholder addition with no behavioral or test impact.
@stdlib-js/reviewers
Generated by Claude Code