-
Notifications
You must be signed in to change notification settings - Fork 230
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
Chore (upgrade eslint config and packages) #3409
Chore (upgrade eslint config and packages) #3409
Conversation
💚 CLA has been signed |
"eslint-plugin-license-header": "^0.6.0", | ||
"eslint-plugin-node": "^11.1.0", | ||
"eslint-plugin-promise": "^4.3.1", | ||
"eslint-plugin-standard": "^4.1.0", |
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.
no longer needed with this eslint-config-standard
i have now signed cla |
Hi @jmetev1. Thanks very much for the PR. There are a lot of changes here, including lint/style changes, so I have a fair amount of feedback. no-varWe discussed internally for a bit, and we'd like to keep this off. I.e. we'd like to not take the large set of changes to switch to array-callback-returnI'd like to keep this set to "error", and then revisit the few places we hit this:
Coordinating
|
I'm afraid with this patch you've gone out of my git depth. I tried to google but am unsure if this is something I'm supposed to be able to apply automatically. But feel free to update my branch. |
Will do. Thanks. |
but i am curious, what was i supposed to do with your gist? i was looking around here, but had no luck https://gist.github.com/nepsilon/22bc62a23f785716705c |
This reverts commit 1727021.
That gist has it right. You would have needed to download my gist to a file (using the "Raw" link): https://gist.githubusercontent.com/trentm/d610966e3cdd02ec8ff810f1b30da511/raw/10433a76f380c9724b932fe0ef9205dc97940375/the.patch |
ohhhh i forget about raw option. i tried that but without raw part. |
@elasticmachine, run elasticsearch-ci/docs |
@elasticmachine, run elasticsearch-ci/docs |
Thanks very much @jmetev1 |
no problem |
The upgrade to eslint@8 in #3409 subtly broken peer-dependencies. `npm ls` unhelpfully does not complain, but `npm ls -a` shows some errors, and `./dev-utils/make-distribution.sh` was broken. The upgrade bumped "eslint-config-standard" from ^14.1.1 to ^16. However, v16 has: "peerDependencies": { "eslint": "^7.12.1", "eslint-plugin-import": "^2.22.1", "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^4.2.1 || ^5.0.0" }, so is incompatible with eslint@8. We need eslint-config-standard@17, which has: "peerDependencies": { "eslint": "^8.0.1", "eslint-plugin-import": "^2.25.2", "eslint-plugin-n": "^15.0.0 || ^16.0.0 ", "eslint-plugin-promise": "^6.0.0" }, Note that also requires a change from eslint-plugin-node (unmaintained) to the replacement "eslint-plugin-n".
The upgrade to eslint@8 in #3409 subtly broke peer-dependencies. `npm ls` unhelpfully does not complain, but `npm ls -a` shows some errors, and `./dev-utils/make-distribution.sh` was broken. The upgrade bumped "eslint-config-standard" from ^14.1.1 to ^16. However, v16 has: "peerDependencies": { "eslint": "^7.12.1", "eslint-plugin-import": "^2.22.1", "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^4.2.1 || ^5.0.0" }, so is incompatible with eslint@8. We need eslint-config-standard@17, which has: "peerDependencies": { "eslint": "^8.0.1", "eslint-plugin-import": "^2.25.2", "eslint-plugin-n": "^15.0.0 || ^16.0.0 ", "eslint-plugin-promise": "^6.0.0" }, Also: - eslint-plugin-node (unmaintained) is replaced by "eslint-plugin-n" - eslint-config-standard@17 added https://eslint.org/docs/latest/rules/object-shorthand as a warning. It'll become "error" in a subsequent major. - eslint@8 means support for top-level await, so there are some files we no longer need to skip
We have turned *off* the "no-var" rule that was added to the "standard" config with this upgrade. See .eslintrc.json for justification. We are applying "no-var" in examples/... Using eslint@8 bumps the min node for linting to 12.20.0. Co-authored-by: Trent Mick <trent.mick@elastic.co>
…ic#3449) The upgrade to eslint@8 in elastic#3409 subtly broke peer-dependencies. `npm ls` unhelpfully does not complain, but `npm ls -a` shows some errors, and `./dev-utils/make-distribution.sh` was broken. The upgrade bumped "eslint-config-standard" from ^14.1.1 to ^16. However, v16 has: "peerDependencies": { "eslint": "^7.12.1", "eslint-plugin-import": "^2.22.1", "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^4.2.1 || ^5.0.0" }, so is incompatible with eslint@8. We need eslint-config-standard@17, which has: "peerDependencies": { "eslint": "^8.0.1", "eslint-plugin-import": "^2.25.2", "eslint-plugin-n": "^15.0.0 || ^16.0.0 ", "eslint-plugin-promise": "^6.0.0" }, Also: - eslint-plugin-node (unmaintained) is replaced by "eslint-plugin-n" - eslint-config-standard@17 added https://eslint.org/docs/latest/rules/object-shorthand as a warning. It'll become "error" in a subsequent major. - eslint@8 means support for top-level await, so there are some files we no longer need to skip
fixes #2583
I updated linting packages. And of course that comes with some changes. I broke up the autofixes vs manual fixes by commit. Autofix did some of the vars, but not all of them. What do you want to do with 144 remaining?
Also i see you're hiring. Can i get a referral?
Checklist