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.
Hello lovely humans,
eslint just published its new version 2.13.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
never
option forfunc-names
(fixes #6059) (#6392) (alberto)padded-blocks
(fixes #6320) (#6393) (alberto)--print-config
return config inside subdir (fixes #6329) (#6385) (alberto)object-curly-newline
multiline with comments (fixes #6381) (#6396) (Toru Nagashima)newline-per-chained-call
message (fixes #6340) (#6360) (Toru Nagashima)espree
instead ofesprima
(#6404) (alberto)fix
param clearer (fixes #6366) (#6367) (Nick Heiner)extends
with relative path (fixes #6358) (#6359) (Toru Nagashima)max-lines
option: fixskipComments
typo (#6374) (Jordan Harband)The new version differs by 90 commits .
414206c
2.13.0
3e5efe0
Build: package.json and changelog update for 2.13.0
cf223dd
Fix: add test for a syntax error (fixes #6013) (#6378)
da30cf9
Update: Add fixer for object-shorthand (fixes #6412) (#6418)
2cd90eb
Chore: Fix rule meta description inconsistencies (refs #5417) (#6422)
d798b2c
Added quotes around "classes" option key (#6441)
852b6df
Docs: Delete empty table of links from Code Path Analysis (#6423)
5e9117e
Chore: sort rules in eslint.json (fixes #6425) (#6426)
c2b5277
Docs: Add gitter chat link to Reporting Bugs (#6430)
1316db0
Update: Add
never
option forfunc-names
(fixes #6059) (#6392)1c123e2
Update: Add autofix for
padded-blocks
(fixes #6320) (#6393)8ec89c8
Fix:
--print-config
return config inside subdir (fixes #6329) (#6385)4f73240
Fix:
object-curly-newline
multiline with comments (fixes #6381) (#6396)77697a7
Chore: Fake config hierarchy fixtures (fixes #6206) (#6402)
73a9a6d
Docs: Fix links in Configuring ESLint (#6421)
There are 90 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade