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-plugin-react.
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 76.829% when pulling e9324ed411da63f6e06e5ede7329d15aa4f51133 on greenkeeper-eslint-plugin-react-6.2.0 into b28a7fe270b7caae516f53dd87463923d66d6056 on master.
Hello lovely humans,
eslint-plugin-react just published its new version 6.2.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-plugin-react. 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
Added
no-unused-prop-types
rule (#226 @EvNaverniouk)style-prop-object
rule (#715 @petersendidit)self-closing-comp
(#770 @pl12133)typeAnnotations
insort-comp
(#235 @dozoisch)PureComponent
inprefer-stateless-function
(#781 @tiemevanveen)Fixed
jsx-uses-vars
to work better withprefer-const
. You'll need to upgrade to ESLint 3.4.0 to completely fix the compatibility issue (#716)require-render-return
crash (#784)prop-types
(#735)Changed
The new version differs by 160 commits .
80fd8e1
Update CHANGELOG and bump version
953e858
Add test to check jsx-uses-vars and prefer-const compatibility (#716)
33a3516
Update dependencies
ed1f168
Adds no-unused-prop-types rule (fixes #226)
466bb5e
Fix require-render-return crash (fixes #784)
7024678
Add PureComponent support to prefer-stateless-function
d4dee48
Fix jsx-uses-vars to work better with prefer-const (fixes #716)
70bf28d
Fix component detection to ignore functions expression without a parent component
7ed3b29
Add style-prop-object rule (fixes #715)
8ea2d0e
Fix related components detection in prop-types (fixes #735)
4be546a
Add backticks to jsx-no-target-blank heading
d89bc05
Add auto fix for self-closing-comp
3a8bf42
Add support for typeAnnotations in sort-comp (fixes #235)
055ea4d
Update CHANGELOG and bump version
7e7b406
Remove deprecated require-extension rule from README
There are 160 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade