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 98.901% when pulling 33ebc28da16e945bd2cf99492887eb7db76e4009 on greenkeeper-eslint-3.4.0 into 75c3636b0a0e0a439c390a5bd33028f48189bbde on master.
Hello lovely humans,
eslint just published its new version 3.4.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-const
false negative abouteslintUsed
(fixes #5837) (#6971) (Toru Nagashima)indent
withelse if
statements (fixes #6956) (#6965) (not-an-aardvark)object-curly-spacing
for type annotations (fixes #6940) (#6945) (Toru Nagashima)@scope/plugin/ruleId
-style specifier (refs #6362) (#6939) (Toru Nagashima)symbol-description
rule (fixes #6778) (#6825) (Jarek Rencz)requireStringLiterals
option forvalid-typeof
(fixes #6698) (#6923) (not-an-aardvark)no-trailing-spaces
wrong fixing (fixes #6933) (#6937) (Toru Nagashima)class-methods-use-this
rule (fixes #5139) (#6881) (Gyandeep Singh)The new version differs by 24 commits .
faab36e
3.4.0
609ed97
Build: package.json and changelog update for 3.4.0
c210510
Update: add fixer for no-extra-parens (fixes #6944) (#6950)
ca3d448
Fix:
prefer-const
false negative abouteslintUsed
(fixes #5837) (#6971)1153955
Docs: Draft of JSCS migration guide (refs #5859) (#6942)
3e522be
Fix: false negative of
indent
withelse if
statements (fixes #6956) (#6965)2dfb290
Docs: Distinguish examples in rules under Stylistic Issues part 7 (#6760)
3c710c9
Fix: rename "AirBnB" => "Airbnb" init choice (fixes #6969)
7660b39
Fix:
object-curly-spacing
for type annotations (fixes #6940) (#6945)21ab784
New: do not remove non visited files from cache. (fixes #6780) (#6921)
3a1763c
Fix: enable
@scope/plugin/ruleId
-style specifier (refs #6362) (#6939)d6fd064
Update: Add never option to multiline-ternary (fixes #6751) (#6905)
0d268f1
New:
symbol-description
rule (fixes #6778) (#6825)a063d4e
Fix: no-cond-assign within a function expression (fixes #6908) (#6909)
16db93a
Build: Tag docs, publish release notes (fixes #6892) (#6934)
There are 24 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade