The version 7.0.0 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.
Add warnings for React.PropTypes and React.createClass in no-deprecated (#1148@Calyhre)
Update createClass component factory to createReactClass. This is used for React component detection, if you still using React.createClass use the shared settings to specify createClass as component factory
Deprecate jsx-space-before-closing rule, use the jsx-tag-spacing rule instead. jsx-space-before-closing still works but will trigger a warning (#1070@afairb)
jsx-first-prop-new-line default is now multiline-multiprop (#802@kokarn)
jsx-wrap-multilines now checks arrow functions without block body. It can be deactivated in rule options (#790@ColCh)
jsx-no-undef will not check the global scope by default. You can force it with the allowGlobals option (#1013@jomasti)
Fixed
Fix no-unused-prop-types false positive with nextProps (#1079@Kerumen)
Fix prefer-stateless-function to not warn on classes with decorators (#1034@benstepp)
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 91.346% when pulling 19e1f244e11e7f918f8ca92e25f058503ef0be1b on greenkeeper/eslint-plugin-react-7.0.0 into b4e6e08dd707ece552ba0c67cb0a751716956801 on master.
Version 7.0.0 of eslint-plugin-react just got published.
The version 7.0.0 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.
Release Notes
v7.0.0Added
no-will-update-set-state
rule (#1139 @ManThursday)no-deprecated
reservedFirst
option tojsx-sort-props
(#1134 @MatthewHerbst)Breaking
React.PropTypes
andReact.createClass
inno-deprecated
(#1148 @Calyhre)createClass
component factory tocreateReactClass
. This is used for React component detection, if you still usingReact.createClass
use the shared settings to specifycreateClass
as component factoryno-danger-with-children
rule to recommended rules (#748 @ljharb)no-string-refs
rule to recommended rules (#749 @ljharb)jsx-key
rule to recommended rules (#750 @ljharb)jsx-no-comment-textnodes
rule to recommended rules (#751 @ljharb)jsx-no-target-blank
rule to recommended rules (#752 @ljharb)no-unescaped-entities
rule to recommended rules (#841 @ljharb)no-children-prop
rule to recommended rules (#842 @ljharb)wrap-multilines
rule, usejsx-wrap-multilines
insteadno-comment-textnodes
rule, usejsx-no-comment-textnodes
insteadrequire-extension
rule, use the eslint-plugin-importextensions
rule insteadjsx-space-before-closing
rule, use thejsx-tag-spacing
rule instead.jsx-space-before-closing
still works but will trigger a warning (#1070 @afairb)jsx-first-prop-new-line
default is nowmultiline-multiprop
(#802 @kokarn)jsx-wrap-multilines
now checks arrow functions without block body. It can be deactivated in rule options (#790 @ColCh)jsx-no-undef
will not check the global scope by default. You can force it with theallowGlobals
option (#1013 @jomasti)Fixed
no-unused-prop-types
false positive withnextProps
(#1079 @Kerumen)prefer-stateless-function
to not warn on classes with decorators (#1034 @benstepp)Changed
Commits
The new version differs by 58 commits0.
d335b1f
Update CHANGELOG and bump version
d97e5f0
Merge pull request #1167 from Slumber86/master
79415f1
Wrong import
48a397e
Fix syntax error
2cd9e5e
Update docs for deprecated prop-types
4d5faee
Update CHANGELOG and bump version
dfe190b
Merge pull request #1134 from MatthewHerbst/jsx-sort-props/new-rule-option--reservedFirst
14dbf99
Merge pull request #802 from kokarn/master
7d08955
Add default for jsx-first-prop-new-line
21ed801
Fix lint errors
b5856ca
Merge pull request #791 from Lingvokot/790-stateless-multiline-wrap
77048c8
Remove deprecated wrap-multilines rule
6d6d24a
Remove deprecated no-comment-textnodes rule
229cc21
Remove deprecated require-extension rule
ed928c2
Merge pull request #1013 from jomasti/jsx-no-undef-imported-only
There are 58 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: