Update eslint-plugin-react to version 6.0.0 🚀 #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 ✨
You rock!
🌴
GitHub Release
Added
allsharable configuration with all rules enabled (#674 @pfhayes)no-find-dom-noderule (#678)shorthandFirstoption tojsx-sort-props(#391 @mathieumg)allowDecoratorsoption torequire-optimization(#669 @Tom910)Breaking
require-extensionrule, use the eslint-plugin-importextensionsrule instead.require-extensionstill works but will trigger a warningallow-in-funcmode by default inno-did-mount-set-stateandno-did-update-set-staterules (#702 @lencioni)self-closing-comppragmaoption fromjsx-uses-react, use the shared settings to specify a custom pragma (#700 @lencioni)reactoption fromno-deprecatedrule, use the shared settings to specify the React version (#700 @lencioni)require-render-returnrule to recommended rulesno-dangerfrom recommended rules (#636 @mjackson)no-did-mount-set-stateandno-did-update-set-statefrom recommended rules (#596)jsx-sort-prop-typesrule, usesort-prop-typesinstead (#549 @lencioni)no-comment-textnodestojsx-no-comment-textnodes.no-comment-textnodesstill works but will trigger a warning (#668 @lencioni)wrap-multilinestojsx-wrap-multilines.wrap-multilinesstill works but will trigger a warning (#668 @lencioni)Fixed
jsx-handler-namesincorrectly flaggingonly(#571 @lencioni)jsx-no-target-blank(#679 @randycoulman)require-optimizationwarning on stateless components (#687)jsx-uses-varsthat incorrectly marked some variables as used (#694 @lencioni)no-unknown-propertycheck on SVG attributes (#718)jsx-no-bindreporting errors on render functions that don't return JSX (#663 @petersendidit)jsx-closing-bracket-locationautofix whenlocationis set toprops-aligned(#684 @pfhayes)prop-typesfor destructured arguments being assigned to the parent stateless component in some cases (#698)prop-typesfor JSX return being assigned to the parent function in some cases (#504)jsx-curly-spacingfor reporting on JSX content by mistake (#671)prop-typescrash when accessing constructor on props (#654)jsx-filename-extensionto not check filenames on text input (#662 @ljharb)jsx-no-comment-textnodesincorrectly catching urls (#664 @petersendidit)Changed
jsx-filename-extensionwarning once per file (#660 @mathieumg)no-unknown-propertyThe new version differs by 59 commits .
9abc070Update CHANGELOG and bump version906c96dUpdate CHANGELOG and bump versiond19d0d5Revert "Completing cleanup ofno-comment-textnodesrule."99f5eacFix wrap-multilines rule1a1dcdbPrevent jsx-handler-names from incorrectly flaggingonly2f7a462Completing cleanup ofno-comment-textnodesrule.bf35995Update CHANGELOG and bump version19ece14Update dependencies4c94f32Update self-closing-comp to check html tags by defaulte84af68Add require-render-return rule to recommended configuration936c42aDeprecate require-extension rule21f684aAdd rules metadata docsa566536Update SVG and DOM attribute list for no-unknown-property34c8a10Fix no-unknown-property check on SVG attributes (fixes #718)095968cDon't include deprecated rules inallconfigThere are 59 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade