Update eslint-plugin-react to the latest version 🚀 #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
Update to this version instead 🚀 Release Notes for v7.12.4Fixed
ChangedCommitsThe new version differs by 10 commits.
See the full diff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The devDependency eslint-plugin-react was updated from
7.12.2to7.12.3.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Release Notes for v7.12.3
Fixed
jsx-indent: Prevent crash on valueless props (#2120, @jomasti)jsx-fragments: avoid crashing on self-closing fragments (#2113, @alexzherdev)no-unused-prop-types: Fix propType detection inside class bodies (#2115, @drx)no-unused-prop-types: fix issue with propTypes misclassifying props (#2111, @drx)display-name: fix false positive forReact.memo(#2109, @jomasti)Changed
Commits
The new version differs by 14 commits.
2f5cec9Update CHANGELOG and bump version096161aMerge pull request #2120 from jomasti/issue-21199d3955aPrevent crash of jsx-indent rule230c7e0Merge pull request #2117 from haideralsh/patch-1b4b0e72fix: add a missing in the JSON settingsd2aa260Merge pull request #2115 from drx/class_body_prop_types41974e5Fix propType detection inside class bodies40f2565[Docs] update README to document React version detectiondd0757fMerge pull request #2113 from alexzherdev/2112-fix-self-closing-fragmentse997f6c[Fix] avoid crashing on self-closing fragmentsb48b479Merge pull request #2111 from drx/prop_types_class_propertiese15bafa[Fix]no-unused-prop-types: fix issue with propTypes misclassifying propsa86b339Merge pull request #2109 from jomasti/issue-21055f9863eFix display-name false positive for React.memoSee the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴