This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage remained the same at 84.393% when pulling 3c3bcd69e84f759f11392169b704f170288345d0 on greenkeeper-eslint-3.7.0 into f79c705ca39690c6a98c86d1573e1a3d4461e46f on master.
Coverage remained the same at 84.393% when pulling 3c3bcd69e84f759f11392169b704f170288345d0 on greenkeeper-eslint-3.7.0 into f79c705ca39690c6a98c86d1573e1a3d4461e46f on master.
Hello lovely humans,
eslint just published its new version 3.7.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
prefer-numeric-literals
(#7205) (Teddy Katz)no-undef-init
(#7210) (Teddy Katz)no-unused-vars
false positive (fixes #7250) (#7258) (Toru Nagashima)indent
handles nested functions correctly (fixes #7249) (#7265) (Teddy Katz)no-useless-computed-key
(#7207) (Teddy Katz)lines-around-directive
(#7217) (Teddy Katz)wrap-iife
(#7196) (Teddy Katz)dot-location
(#7186) (Teddy Katz)yoda
, add a fixer (#7199) (Teddy Katz)no-extra-parens
false negative (fixes #7229) (#7231) (Teddy Katz)The new version differs by 325 commits .
029e844
3.7.0
d334663
Build: package.json and changelog update for 3.7.0
2fee8ad
Fix: object-shorthand's consistent-as-needed option (issue #7214) (#7215)
c05a19c
Update: add fixer for
prefer-numeric-literals
(#7205)2f171f3
Update: add fixer for
no-undef-init
(#7210)876d747
Docs: Steps for adding new committers/TSCers (#7221)
dffb4fa
Fix:
no-unused-vars
false positive (fixes #7250) (#7258)4448cec
Docs: Adding missing ES8 reference to configuring (#7271)
332d213
Update: Ensure
indent
handles nested functions correctly (fixes #7249) (#7265)c36d842
Update: add fixer for
no-useless-computed-key
(#7207)18376cf
Update: add fixer for
lines-around-directive
(#7217)f8e8fab
Update: add fixer for
wrap-iife
(#7196)558b444
Docs: Add @not-an-aardvark to development team (#7279)
cd1dc57
Update: Add a fixer for
dot-location
(#7186)89787b2
Update: for
yoda
, add a fixer (#7199)There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade