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
applyDefaultPatternsinline-comment-position(#8183) (alberto)+ +ato++ain space-unary-ops (#8176) (Alan Pierce)coverallsto ^2.11.16 (#8161) (alberto)createinno-use-before-define(#8166) (Justin Anastos)linefixandgh-got(#8160) (alberto)lines-around-commentdoesn't disallow empty lines (#8151) (alberto)ignoreRestSiblingsoption didn't cover arguments (fixes #8119) (#8120) (Toru Nagashima)The new version differs by 839 commits .
f882a113.17.06748c18Build: package.json and changelog update for 3.17.04fdf6d7Update: deprecateapplyDefaultPatternsinline-comment-position(#8183)25e5817Fix: Don't autofix+ +ato++ain space-unary-ops (#8176)a6ce8f9Build: Sort rules before dumping them to doc files (#8154)0af9057Chore: Upgrade to a patched version of mock-fs (fixes #8177) (#8188)bf4d8cfUpdate: ignore eslint comments in lines-arount-comment (fixes #4345) (#8155)dad20adNew: add SourceCode#getLocFromIndex and #getIndexFromLoc (fixes #8073) (#8158)18a519fUpdate: let RuleTester cases assert that no autofix occurs (fixes #8157) (#8163)a30eb8dDocs: improve documentation for RuleTester cases (#8162)a78ec9fChore: upgradecoverallsto ^2.11.16 (#8161)d02bd11Fix: padded-blocks autofix problems with comments (#8149)9994889Docs: Add missing space tocreateinno-use-before-define(#8166)4d542baDocs: Remove unneeded statement about autofix (#8164)20daea5New: 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.