-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
[v16.x] Fix JS linting warnings and errors #41805
Closed
Closed
+7
−11
Conversation
This file contains 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
nodejs-github-bot
added
lib / src
Issues and PRs related to general changes in the lib or src directory.
needs-ci
PRs that need a full CI run.
labels
Feb 1, 2022
danielleadams
changed the title
Fix JS linting warnings and errors
[v16.x] Fix JS linting warnings and errors
Feb 1, 2022
targos
reviewed
Feb 1, 2022
lib/internal/blob.js
Outdated
@@ -131,7 +131,7 @@ class Blob { | |||
* endings? : string, | |||
* type? : string, | |||
* }} [options] | |||
* @returns | |||
* @returns {any} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
* @returns {any} | |
* @constructs {Blob} |
(same commit for other @returns
changes)
Maybe the commit can be cherry-picked without trouble now?
targos
reviewed
Feb 1, 2022
danielleadams
force-pushed
the
da/fix-js-lint
branch
from
February 1, 2022 12:26
75896f7
to
88f8e97
Compare
danielleadams
added
the
fast-track
PRs that do not need to wait for 48 hours to land.
label
Feb 1, 2022
Fast-track has been requested by @danielleadams. Please 👍 to approve. |
danielleadams
force-pushed
the
da/fix-js-lint
branch
from
February 1, 2022 12:29
88f8e97
to
cdfbef2
Compare
targos
approved these changes
Feb 1, 2022
danielleadams
force-pushed
the
da/fix-js-lint
branch
from
February 1, 2022 13:01
cdfbef2
to
58f1200
Compare
This was referenced Feb 2, 2022
This was referenced Feb 4, 2022
@nodejs/collaborators anyone around to give a 👍🏼 ? |
aduh95
approved these changes
Feb 5, 2022
Trott
approved these changes
Feb 5, 2022
Mesteery
approved these changes
Feb 5, 2022
danielleadams
added a commit
that referenced
this pull request
Feb 5, 2022
PR-URL: #41805 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Rich Trott <[email protected]>
danielleadams
added a commit
that referenced
this pull request
Feb 5, 2022
PR-URL: #41805 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Landed in ebc370c...1de552c |
27 tasks
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
fast-track
PRs that do not need to wait for 48 hours to land.
lib / src
Issues and PRs related to general changes in the lib or src directory.
needs-ci
PRs that need a full CI run.
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.
When creating #41804, I ran into some linting exceptions. I'm not sure if any of these are fixed in master, but for the purposes of getting the release out, I wanted to fix them in v16.x-staging since they were easy changes.