Skip to content

"chore: fix JavaScript lint errors (issue #6616)". #6619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

GURUPRASADSHARMA
Copy link
Contributor

@GURUPRASADSHARMA GURUPRASADSHARMA commented Apr 9, 2025

linting error coming because use WARNING keyword in comment which is not allowed to use explicitly

Resolves #{{TODO: resolved #6616}}.

Description

What is the purpose of this pull request?

This pull request:

  • {{TODO: resolving linting error generated bacause use of WARNING keyword in comment }}

Related Issues

Does this pull request have any related issues?

This pull request:

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.


@stdlib-js/reviewers

linting error coming because use WARNING keyword in comment which is not allowed to use explicitly

Signed-off-by: GURU PRASAD SHARMA <[email protected]>
@stdlib-bot stdlib-bot added 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. Good First PR A pull request resolving a Good First Issue. labels Apr 9, 2025
@stdlib-bot
Copy link
Contributor

Coverage Report

Package Statements Branches Functions Lines
strided/base/unary-addon-dispatch $\color{green}439/439$
$\color{green}+100.00\%$
$\color{green}59/59$
$\color{green}+100.00\%$
$\color{green}4/4$
$\color{green}+100.00\%$
$\color{green}439/439$
$\color{green}+100.00\%$

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

@kgryte kgryte added Needs Changes Pull request which needs changes before being merged. and removed Needs Review A pull request which needs code review. labels Apr 9, 2025
@kgryte
Copy link
Member

kgryte commented Apr 9, 2025

@GURUPRASADSHARMA Ignore the warning. However, you can fix the error identified in that issue for number/float32/base/to-word.

@stdlib-bot stdlib-bot removed the First-time Contributor A pull request from a contributor who has never previously committed to the project repository. label Apr 14, 2025
@kgryte
Copy link
Member

kgryte commented Apr 14, 2025

Ref: #6626

@kgryte kgryte added the autoclose: Already Resolved Pull request which should be auto-closed due proposed changes duplicating already included changes. label Apr 14, 2025
@stdlib-bot
Copy link
Contributor

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 Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autoclose: Already Resolved Pull request which should be auto-closed due proposed changes duplicating already included changes. Good First PR A pull request resolving a Good First Issue. Needs Changes Pull request which needs changes before being merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix JavaScript lint errors
3 participants