Skip to content
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

tools: specify ESLint rules being disabled in two files #22563

Closed
wants to merge 2 commits into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Aug 28, 2018

Instead of disabling all ESLint rules, just disable the rules necessary.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@Trott Trott added the tools Issues and PRs related to the tools directory. label Aug 28, 2018
@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Aug 28, 2018
@Trott
Copy link
Member Author

Trott commented Aug 28, 2018

Can't seem to start a full CI at the moment, but perhaps the Lite CI is enough since this changes comments only, so linting is the thing to check?

@Trott Trott added the fast-track PRs that do not need to wait for 48 hours to land. label Aug 28, 2018
@Trott
Copy link
Member Author

Trott commented Aug 28, 2018

Please 👍 here for fast-tracking.

@vsemozhetbyt
Copy link
Contributor

Something wrong with CI lite (rebasing?) happens now. In this PR CI lite has a wrong commit:

https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/710/

(In this PR last CI lite had many wrong commits: #22170)

@@ -692,7 +692,7 @@ common.expectsError(
() => {
a(
(() => 'string')()
// eslint-disable-next-line
// eslint-disable-next-line operator-linebreak
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI is failing because the message check in L701-L712 needs to be updated to match.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Argh! Fixed.

@@ -716,7 +716,7 @@ common.expectsError(
() => {
a(
(() => 'string')()
// eslint-disable-next-line
// eslint-disable-next-line operator-linebreak
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI is failing because the message check in L725-L736 needs to be updated to match.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also: Argh! Fixed.

Instead of disabling all ESLint rules for a line, specify the two rules
that should be disabled.
Instead of disabling all ESLint rules on two lines in test-assert.js,
specify the rule that needs to be disabled.
@Trott
Copy link
Member Author

Trott commented Aug 29, 2018

@Trott
Copy link
Member Author

Trott commented Aug 31, 2018

@BridgeAR BridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Aug 31, 2018
@addaleax
Copy link
Member

Landed in c5bd856, f86d0eb

@addaleax addaleax closed this Aug 31, 2018
addaleax pushed a commit that referenced this pull request Aug 31, 2018
Instead of disabling all ESLint rules for a line, specify the two rules
that should be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
addaleax pushed a commit that referenced this pull request Aug 31, 2018
Instead of disabling all ESLint rules on two lines in test-assert.js,
specify the rule that needs to be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
addaleax pushed a commit that referenced this pull request Aug 31, 2018
Instead of disabling all ESLint rules for a line, specify the two rules
that should be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
addaleax pushed a commit that referenced this pull request Aug 31, 2018
Instead of disabling all ESLint rules on two lines in test-assert.js,
specify the rule that needs to be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
targos pushed a commit that referenced this pull request Sep 3, 2018
Instead of disabling all ESLint rules for a line, specify the two rules
that should be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
targos pushed a commit that referenced this pull request Sep 3, 2018
Instead of disabling all ESLint rules on two lines in test-assert.js,
specify the rule that needs to be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
targos pushed a commit that referenced this pull request Sep 6, 2018
Instead of disabling all ESLint rules for a line, specify the two rules
that should be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
targos pushed a commit that referenced this pull request Sep 6, 2018
Instead of disabling all ESLint rules on two lines in test-assert.js,
specify the rule that needs to be disabled.

PR-URL: #22563
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
@Trott Trott deleted the no-abusive-eslint-disable branch October 10, 2021 01:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. fast-track PRs that do not need to wait for 48 hours to land. test Issues and PRs related to the tests. tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants