Skip to content

fix: resolve eslint violations in to_array.js and test.ndarray.js - #13911

Open
protestershankar wants to merge 2 commits into
stdlib-js:developfrom
protestershankar:fix/eslint-lint-random-files-issues
Open

fix: resolve eslint violations in to_array.js and test.ndarray.js#13911
protestershankar wants to merge 2 commits into
stdlib-js:developfrom
protestershankar:fix/eslint-lint-random-files-issues

Conversation

@protestershankar

Copy link
Copy Markdown
Contributor

Resolves N/A.

Description

What is the purpose of this pull request?

This pull request:

  • Fixes two ESLint violations flagged by the scheduled lint_random_files workflow: a stdlib/no-new-array violation in to_array.js (replaced the new Array() constructor with an array literal and push), and a stdlib/no-empty-lines-between-requires violation in test.ndarray.js (removed an empty line between two require statements).

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

  • None. These issues were identified via the scheduled lint_random_files CI workflow rather than a filed issue.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of 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

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance.

I used Claude (Anthropic) to help identify the ESLint rule violations from the CI logs and to draft the corrected code, which I then reviewed and applied myself.


@stdlib-js/reviewers

@protestershankar
protestershankar requested a review from a team August 4, 2026 10:49
@stdlib-bot stdlib-bot added the Needs Review A pull request which needs code review. label Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs Review A pull request which needs code review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants