-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Update ESLint, replace custom rule with built-in #8478
Closed
Closed
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
ESLint 3.5.0 introduces a `no-restricted-properties` rule. Replace our custom `no-deepEqual` rule with this rule.
nodejs-github-bot
added
assert
Issues and PRs related to the assert subsystem.
child_process
Issues and PRs related to the child_process subsystem.
labels
Sep 10, 2016
LGTM if CI is green. |
Trott
added a commit
to Trott/io.js
that referenced
this pull request
Sep 13, 2016
PR-URL: nodejs#8478 Reviewed-By: James M Snell <[email protected]>
Trott
added a commit
to Trott/io.js
that referenced
this pull request
Sep 13, 2016
PR-URL: nodejs#8478 Reviewed-By: James M Snell <[email protected]>
Trott
added a commit
to Trott/io.js
that referenced
this pull request
Sep 13, 2016
ESLint 3.5.0 introduces a `no-restricted-properties` rule. Replace our custom `no-deepEqual` rule with this rule. PR-URL: nodejs#8478 Reviewed-By: James M Snell <[email protected]>
Fishrock123
pushed a commit
that referenced
this pull request
Sep 14, 2016
PR-URL: #8478 Reviewed-By: James M Snell <[email protected]>
Fishrock123
pushed a commit
that referenced
this pull request
Sep 14, 2016
PR-URL: #8478 Reviewed-By: James M Snell <[email protected]>
Fishrock123
pushed a commit
that referenced
this pull request
Sep 14, 2016
ESLint 3.5.0 introduces a `no-restricted-properties` rule. Replace our custom `no-deepEqual` rule with this rule. PR-URL: #8478 Reviewed-By: James M Snell <[email protected]>
@Trott do you want to backport this to lts? |
@thealphanerd I'm inclined to skip it if it doesn't cause you any problems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
assert
Issues and PRs related to the assert subsystem.
child_process
Issues and PRs related to the child_process subsystem.
tools
Issues and PRs related to the tools directory.
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.
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
tools
Description of change
Three commits:
new
keyword is used without parentheses. These are some edge cases that were missed by the previous version of ESLint. Basically, the rule got a bug fix, and now it's finding a tiny bit more stuff in our code.assert.deepEqual()
with a built-in rule that does the same (and seems to find a few uses that our custom rule did not, so that's a plus).