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.
Hello lovely humans,
eslint-plugin-react just published its new version 6.0.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
all
sharable configuration with all rules enabled (#674 @pfhayes)no-find-dom-node
rule (#678)shorthandFirst
option tojsx-sort-props
(#391 @mathieumg)allowDecorators
option torequire-optimization
(#669 @Tom910)Breaking
require-extension
rule, use the eslint-plugin-importextensions
rule instead.require-extension
still works but will trigger a warningallow-in-func
mode by default inno-did-mount-set-state
andno-did-update-set-state
rules (#702 @lencioni)self-closing-comp
pragma
option fromjsx-uses-react
, use the shared settings to specify a custom pragma (#700 @lencioni)react
option fromno-deprecated
rule, use the shared settings to specify the React version (#700 @lencioni)require-render-return
rule to recommended rulesno-danger
from recommended rules (#636 @mjackson)no-did-mount-set-state
andno-did-update-set-state
from recommended rules (#596)jsx-sort-prop-types
rule, usesort-prop-types
instead (#549 @lencioni)no-comment-textnodes
tojsx-no-comment-textnodes
.no-comment-textnodes
still works but will trigger a warning (#668 @lencioni)wrap-multilines
tojsx-wrap-multilines
.wrap-multilines
still works but will trigger a warning (#668 @lencioni)Fixed
jsx-handler-names
incorrectly flaggingonly
(#571 @lencioni)jsx-no-target-blank
(#679 @randycoulman)require-optimization
warning on stateless components (#687)jsx-uses-vars
that incorrectly marked some variables as used (#694 @lencioni)no-unknown-property
check on SVG attributes (#718)jsx-no-bind
reporting errors on render functions that don't return JSX (#663 @petersendidit)jsx-closing-bracket-location
autofix whenlocation
is set toprops-aligned
(#684 @pfhayes)prop-types
for destructured arguments being assigned to the parent stateless component in some cases (#698)prop-types
for JSX return being assigned to the parent function in some cases (#504)jsx-curly-spacing
for reporting on JSX content by mistake (#671)prop-types
crash when accessing constructor on props (#654)jsx-filename-extension
to not check filenames on text input (#662 @ljharb)jsx-no-comment-textnodes
incorrectly catching urls (#664 @petersendidit)Changed
jsx-filename-extension
warning once per file (#660 @mathieumg)no-unknown-property
The new version differs by 59 commits .
9abc070
Update CHANGELOG and bump version
906c96d
Update CHANGELOG and bump version
d19d0d5
Revert "Completing cleanup of
no-comment-textnodes
rule."99f5eac
Fix wrap-multilines rule
1a1dcdb
Prevent jsx-handler-names from incorrectly flagging
only
2f7a462
Completing cleanup of
no-comment-textnodes
rule.bf35995
Update CHANGELOG and bump version
19ece14
Update dependencies
4c94f32
Update self-closing-comp to check html tags by default
e84af68
Add require-render-return rule to recommended configuration
936c42a
Deprecate require-extension rule
21f684a
Add rules metadata docs
a566536
Update SVG and DOM attribute list for no-unknown-property
34c8a10
Fix no-unknown-property check on SVG attributes (fixes #718)
095968c
Don't include deprecated rules in
all
configThere are 59 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade