Update eslint-plugin-react to version 6.10.0 🚀 #159
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.10.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
forbid-foreign-prop-types
rule (#696 @iancmyers)void-dom-elements-no-children
rule (#709 @lencioni)forbid-elements
rule (#887 @kentor)noSortAlphabetically
option tojsx-sort-props
(#541 #786 @markus101)when
option tojsx-max-props-per-line
(#878 @kentor)nextProps
toprop-types
(#814)Fixed
require-default-props
crash (#1029)require-default-props
rule when using Flow type from assignment (#1043 @wyze @CarlRosell)style-prop-object
to not warn with explicitnull
orundefined
(#812 @ljharb)no-unused-prop-types
props detection in stateless components (#885 @BarryThePenguin)display-name
false positive withdocument.createElement
(#996 @jomasti)Changed
The new version differs by 374 commits .
83d4c4b
Update CHANGELOG and bump version
ee144d6
Merge pull request #890 from kentor/forbid-elements
3e2421e
Merge pull request #946 from BarryThePenguin/no-unused-prop-types-in-jsx
3b25a3b
Merge pull request #882 from kentor/jsx-max-props-per-line-updates
54abb8b
Merge pull request #1055 from iancmyers/icm-forbid-foreign-prop-type
0b25b66
Add forbid-foreign-prop-types rule
c586273
Merge pull request #1062 from dguo/patch-2
8e207b8
Fix no-array-index-key typo
d884a98
Add new rule: forbid-elements
c97dd0f
Merge pull request #1051 from yannickcr/void-dom-elements-no-children
a84d5f5
jsx-max-props-per-line: Use json format in docs
9af8d25
fix comments
d5c3e91
detect used props in jsx
b52f3b8
jsx-max-props-per-line: Add additional test cases
b485e28
jsx-max-props-per-line: Add
when
optionThere are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.