Update eslint-plugin-react to the latest version 🚀 #88
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.
Version 7.2.0 of eslint-plugin-react just got published.
The version 7.2.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.2.0Added
no-unused-state
rule (#1103 @wbinnssmith)boolean-prop-naming
rule (#1264 @EvHaus)no-typos
rule (#1189 @jseminck, #1294 @haridusenadeera)sort-props
(#1273 @Overload119)getters
andsetters
groups tosort-comp
(#100 @RDGthree)noStrings
option tono-literals
(#1202 @deecewan)always
/never
tojsx-boolean-value
(#1249 @ljharb)Fixed
no-direct-mutation-state
to disallowthis.state
mutation in constructor (#832 @burabure)jsx-no-target-blank
crash on emptyrel
attribute (#1269 @dustinsoftware)sort-comp
component detection withClassExpression
(#1076 @webOS101)no-unused-prop-types
detection with async class properties and methods (#1053 @benstepp)void-dom-elements-no-children
crash (#1226 @kokobeware)no-danger-with-children
to ignore line breaks (#1262)no-danger-with-children
crash with undefined (#1287)jsx-no-target-blank
crash (#1296 @jseminck)no-unused-props
to no longer ignore components with no used props (#1303 @DianaSuvorova)jsx-no-duplicate-props
crash (#969 @marcelmokos)no-literals
false positives (#1301 @davidyorr)no-find-dom-node
detection with named imports (#785 @Hypnosphi)no-unused-prop-types
detection with propTypes wrapped in a function (#1253 @dustinsoftware)no-unused-prop-types
detection with destructured use of properties (#816 @DianaSuvorova)no-unused-prop-types
detection with inline functions (#1309 @DianaSuvorova)no-unused-prop-types
skipShapeProps
option with Flow annotations (#1335 @DianaSuvorova)jsx-curly-spacing
schema incompatibility with ESLint 4.2.0 (#1290 @jseminck)Changed
Commits
The new version differs by 153 commits.
73abadb
Update CHANGELOG and bump version
1a622ea
Merge pull request #1343 from DianaSuvorova/unusedPropsFlow
f9c22ef
Merge pull request #1273 from Overload119/master
d66808b
Modernize to use let and const
e305279
Merge pull request #1344 from DianaSuvorova/docs
15d0f74
[no-unused-prop-types] test from #933
f446335
[no-unused-prop-types] known false positives doc
95acd93
Merge pull request #1341 from DianaSuvorova/flowShape
942e594
flow should respect skipShapeProps
f0487f2
Merge pull request #1338 from DianaSuvorova/graphql
b6bd2da
[no-unused-prop-types] graphql issue #1097
df84876
Update dependencies
a19eec6
Merge pull request #1294 from haridusenadeera/master
ed72341
Merge pull request #1329 from DianaSuvorova/docs
3195805
Merge pull request #1302 from davidyorr/master
There are 153 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴