chore: fix JavaScript lint errors (issue #10447)#10464
Merged
Planeshifter merged 2 commits intostdlib-js:developfrom Feb 24, 2026
Merged
chore: fix JavaScript lint errors (issue #10447)#10464Planeshifter merged 2 commits intostdlib-js:developfrom
Planeshifter merged 2 commits intostdlib-js:developfrom
Conversation
---
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
- task: lint_filenames
status: passed
- task: lint_editorconfig
status: passed
- task: lint_markdown
status: na
- task: lint_package_json
status: na
- task: lint_repl_help
status: na
- task: lint_javascript_src
status: passed
- task: lint_javascript_cli
status: na
- task: lint_javascript_examples
status: na
- task: lint_javascript_tests
status: na
- task: lint_javascript_benchmarks
status: na
- task: lint_python
status: na
- task: lint_r
status: na
- task: lint_c_src
status: na
- task: lint_c_examples
status: na
- task: lint_c_benchmarks
status: na
- task: lint_c_tests_fixtures
status: na
- task: lint_shell
status: na
- task: lint_typescript_declarations
status: passed
- task: lint_typescript_tests
status: na
- task: lint_license_headers
status: passed
---
lib/node_modules/@stdlib/_tools/eslint/rules/jsdoc-maximum-line-length/lib/main.js
Outdated
Show resolved
Hide resolved
Signed-off-by: Philipp Burckhardt <pburckhardt@outlook.com>
Planeshifter
approved these changes
Feb 24, 2026
Contributor
PR Commit MessagePlease review the above commit message and make any necessary adjustments. |
5 tasks
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.
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:
Resolves #10447.
Description
This pull request:
stdlib/no-new-arraylinting error in@stdlib/_tools/makie/plugins/makie-view-covby replacing theArrayconstructor with an array literal.stdlib/no-unnecessary-nested-functionslinting error in@stdlib/_tools/eslint/rules/jsdoc-maximum-line-lengthby moving thecopyLocationInfofunction to the module scope and adjusting indentation/spacing.Related Issues
This pull request has the following related issues:
Questions
No.
Other
The fixes were verified locally using the following commands:
npx eslint lib/node_modules/@stdlib/_tools/makie/plugins/makie-view-cov/lib/main.js
npx eslint lib/node_modules/@stdlib/_tools/eslint/rules/jsdoc-maximum-line-length/lib/main.js
Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
I consulted Gemini to understand the specific stdlib linting rules and to ensure the function relocation followed the project's architectural patterns, but the final implementation was manually reviewed and verified locally via npx eslint.
@stdlib-js/reviewers