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

V4 eslint 2 #5372

Closed
wants to merge 4 commits into from
Closed

V4 eslint 2 #5372

wants to merge 4 commits into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Feb 22, 2016

Backport of #5214 for v4.x LTS.

/cc @thealphanerd

@mscdex mscdex added tools Issues and PRs related to the tools directory. v4.x labels Feb 23, 2016
@Trott
Copy link
Member Author

Trott commented Feb 24, 2016

/ping @thealphanerd Is this basically what you wanted/needed? Or not quite?

@MylesBorins
Copy link
Contributor

@Trott can you include the original commit messages, including reviewers and other meta data

@Trott
Copy link
Member Author

Trott commented Feb 24, 2016

@thealphanerd Keep the original PR number and don't use this PR number?

@MylesBorins
Copy link
Contributor

indeed... that is what we have done in the past. This PR is simply formalizing the process of rebasing (essentially)

ESLint 2.1.0 is coming. Some lint rules have been tightened.

PR-URL: nodejs#5214
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: jbergstroem - Johan Bergström <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
We are about to upgrade from ESlint 1 to ESLint 2. Remove lint rules
that will not exist in ESLint 2.

PR-URL: nodejs#5214
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: jbergstroem - Johan Bergström <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Update ESLint to 2.1.0. ESLint has a number of potentially-useful new
features but this change attempts to be minimal in its changes.
However, some things could not be avoided reasonably.

ESLint 2.1.0 found a few lint issues that ESLing 1.x missed with
template strings that did not take advantage of any features of
template strings, and `let` declarations where `const` sufficed.

Additionally, ESLint 2.1.0 removes some granularity around enabling ES6
features. Some features (e.g., spread operator) that had been turned off
in our configuration for ESLint 1.x are now permitted.

PR-URL: nodejs#5214
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: jbergstroem - Johan Bergström <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Now that we are using ESLint 2, replace ESLint 1 rules with their ESLint
2 equivalents.

PR-URL: nodejs#5214
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: jbergstroem - Johan Bergström <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
@Trott
Copy link
Member Author

Trott commented Feb 24, 2016

OK, all done.

@MylesBorins
Copy link
Contributor

Ok so this has a weird regression... which is present on master right now.

make test-addons generates files that don't pass the linter

fix is in --> #5425

when that is ready to go in everything can go into LTS together

@MylesBorins
Copy link
Contributor

landed as 7c9b3e1...fcbd551

@Trott Trott deleted the v4-eslint-2 branch January 13, 2022 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants