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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
eslint just published its new version 3.17.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
applyDefaultPatterns
inline-comment-position
(#8183) (alberto)+ +a
to++a
in space-unary-ops (#8176) (Alan Pierce)coveralls
to ^2.11.16 (#8161) (alberto)create
inno-use-before-define
(#8166) (Justin Anastos)linefix
andgh-got
(#8160) (alberto)lines-around-comment
doesn't disallow empty lines (#8151) (alberto)ignoreRestSiblings
option didn't cover arguments (fixes #8119) (#8120) (Toru Nagashima)The new version differs by 1220 commits .
f882a11
3.17.0
6748c18
Build: package.json and changelog update for 3.17.0
4fdf6d7
Update: deprecate
applyDefaultPatterns
inline-comment-position
(#8183)25e5817
Fix: Don't autofix
+ +a
to++a
in space-unary-ops (#8176)a6ce8f9
Build: Sort rules before dumping them to doc files (#8154)
0af9057
Chore: Upgrade to a patched version of mock-fs (fixes #8177) (#8188)
bf4d8cf
Update: ignore eslint comments in lines-arount-comment (fixes #4345) (#8155)
dad20ad
New: add SourceCode#getLocFromIndex and #getIndexFromLoc (fixes #8073) (#8158)
18a519f
Update: let RuleTester cases assert that no autofix occurs (fixes #8157) (#8163)
a30eb8d
Docs: improve documentation for RuleTester cases (#8162)
a78ec9f
Chore: upgrade
coveralls
to ^2.11.16 (#8161)d02bd11
Fix: padded-blocks autofix problems with comments (#8149)
9994889
Docs: Add missing space to
create
inno-use-before-define
(#8166)4d542ba
Docs: Remove unneeded statement about autofix (#8164)
20daea5
New: no-compare-neg-zero rule (#8091)
There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.