Skip to content

chore: fix JavaScript lint errors (issue #11123)#11136

Closed
Dharaneeshsl wants to merge 1 commit intostdlib-js:developfrom
Dharaneeshsl:chore/fix-js-lint-11123
Closed

chore: fix JavaScript lint errors (issue #11123)#11136
Dharaneeshsl wants to merge 1 commit intostdlib-js:developfrom
Dharaneeshsl:chore/fix-js-lint-11123

Conversation

@Dharaneeshsl
Copy link
Copy Markdown

@Dharaneeshsl Dharaneeshsl commented Mar 25, 2026

Resolves #11123.

Description

What is the purpose of this pull request?

This pull request fixes a CI JavaScript lint failure by updating funseqAsync in @stdlib/utils/async/function-sequence to comply with the stdlib/no-new-array ESLint rule.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

Questions

Any questions for reviewers of this pull request?

Yes. I am interested in contributing through GSoC 2026. Could you please share the recommended next steps (e.g., where to follow announcements, how to engage with mentors, and expectations for proposal preparation)?

Other

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

This contribution is part of my Google Summer of Code (GSoC) preparation.

Checklist

Please ensure that 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 ChatGPT to identify the lint rule violation pattern and suggest a compliant replacement. I manually applied and verified the final change before submission.

@stdlib-js/reviewers

@MANDEep22332 MANDEep22332 mentioned this pull request Mar 25, 2026
Closed
7 tasks
@github-actions github-actions bot mentioned this pull request Mar 25, 2026
Open
@kgryte
Copy link
Copy Markdown
Member

kgryte commented Mar 25, 2026

Ref: #11133

@kgryte kgryte added autoclose: Already Resolved Pull request which should be auto-closed due proposed changes duplicating already included changes. and removed autoclose: Already Resolved Pull request which should be auto-closed due proposed changes duplicating already included changes. labels Mar 25, 2026
@stdlib-bot
Copy link
Copy Markdown
Contributor

stdlib-bot commented Mar 25, 2026

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

Next Steps

  1. A project maintainer will approve GitHub Actions workflows for your PR.
  2. All CI checks must pass before your submission can be fully reviewed.
  3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

@stdlib-bot stdlib-bot added Good First PR A pull request resolving a Good First Issue. First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Needs Review A pull request which needs code review. labels Mar 25, 2026
@stdlib-bot
Copy link
Copy Markdown
Contributor

stdlib-bot commented Mar 25, 2026

Thank you for working on this pull request. However, we cannot accept your contribution as the issue this pull request seeks to resolve has already been addressed in a different pull request or commit.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.

@stdlib-bot stdlib-bot closed this Mar 25, 2026
@stdlib-bot
Copy link
Copy Markdown
Contributor

stdlib-bot commented Mar 25, 2026

Coverage Report

No coverage information available.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

autoclose: Already Resolved Pull request which should be auto-closed due proposed changes duplicating already included changes. First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Good First PR A pull request resolving a Good First Issue. Needs Review A pull request which needs code review.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Fix JavaScript lint errors

3 participants

@Dharaneeshsl @kgryte @stdlib-bot