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
ESLint Standard #1335
ESLint Standard #1335
Conversation
A few manual fixes are still needed:
|
These are most likely to be resolved in the future PRs. This is only about auto-fixable stuff for a good foundation, as there is no manual review needed. |
@@ -11,6 +11,7 @@ | |||
"browser": "NODE_ENV=production webpack", | |||
"browser:dev": "webpack", | |||
"build": "npm run clean && npm run cjs && npm run browser", | |||
"lint": "eslint lib test", |
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.
It would be nice to have another npm script format
so future contributor can use it to reformat their code before submitting a PR
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.
in a second thought this might pollute the changes in the PR, adding a ci step to lint would be better I guess
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.
Added linting to test script 🙂
0f77372
to
bb2d866
Compare
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.
👏
Umbrella issue: #1333
Use a unified ESLint config instead of maintaining our own set of rules.
no-var
&prefer-const
has been added, so we get ESLint autofixes for free 🙂Only the first commit needs to be reviewed, as the rest can be considered safe, as the transforms for autofixes are tested by ESLint & the community.