-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
upgrade(package): Update eslint 3.19.0 -> 4.17.0 #2026
Conversation
.eslintrc.yml
Outdated
@@ -254,7 +254,8 @@ rules: | |||
- allowAfterThis: false | |||
object-curly-newline: | |||
- error | |||
- minProperties: 1 | |||
- minProperties: 2 |
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.
Should we expand this to 3?
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.
Sounds good with me
I just noticed, this only updates to 4.16.0, not 4.17.0 – is that intentional? |
4.17.0 must've come out recently – yeah we might as well change it to that then |
It's been out since Feb 2 – how long have you had this branch sitting around? ;P |
@jhermsmeier looks npm is complaining about 4.17.0 – the changelog doesn't seem to have anything crucial for us right now in any case so I'm gonna go ahead and merge this once the tests pass. <@etcher-alt>-<⎇ upgrade-eslint>-<*>-> npm install eslint@latest --dev
npm WARN install Usage of the `--dev` option is deprecated. Use `--only=dev` instead.
etcher@1.3.1 /home/benedict/Prog/Javascript/etcher-alt
└── eslint@4.17.0 invalid |
That's because you're not saving & shrinkwrapping it, also the --dev isn't what you're looking for; you'll want to do the following when updating deps in Etcher:
|
Ah, I got confused with npm's save by default but that doesn't apply to our version of npm. Thanks. |
We upgrade eslint for better support of the object-curly-newline options, and change the quantity of elements required before the linter enforces newlines on objects, in addition we apply `consistent` to avoid errors when there are newlines in objects with less than 2 elements. ``` const { field } = object const { field } = object const { field1, field2 } = object ```` Change-Type: patch Changelog-Entry: Upgrade eslint to use object-curly-newline options.
We upgrade eslint for better support of the object-curly-newline
options, and change the quantity of elements required before the linter
enforces newlines on objects, in addition we apply
consistent
to avoiderrors when there are newlines in objects with less than 2 elements.
Change-Type: patch
Changelog-Entry: Upgrade eslint to use object-curly-newline options.