Update eslint-plugin-react to version 6.10.1 🚀 #77
Conversation
This file contains 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
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.
Hello lovely humans,
eslint-plugin-react just published its new version 6.10.1.
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
Fixed
jsx-indentauto fix with tabs ([#1057][] @kentcdodds @webOS101)jsx-indentcrash ([#1061][] @iancmyers)void-dom-elements-no-childrencrash and fix it to only checks for a createElement call fromReact ([#1073][] @jomasti)
no-multi-comp([#1088][] @benstepp)The new version differs by 418 commits .
ab03af8Update CHANGELOG and bump versionb646485Merge pull request #1089 from benstepp/bs-multicomp-false-positivesc038899Bug fix for false positives with no-multi-comp8148833[Fix] Update void-dom-elements-no-children createElement checksc45ab86Merge pull request #1081 from webOS101/jsx-indent-fix7863a5cFix jsx-indent single line jsx416deffUpdate void-dom-elements-no-children22f3638Merge pull request #1077 from iancmyers/fix-jsx-indent-template-conditionalc6f4a5eFix error caused by templates in ConditionalExpressions (jsx-indent)a4b6a85Merge pull request #1058 from kentcdodds/pr/jsx-indent-tabs-fix83d4c4bUpdate CHANGELOG and bump version6e5f688[Fix] jsx-indent with tabs (fixes #1057)ee144d6Merge pull request #890 from kentor/forbid-elements3e2421eMerge pull request #946 from BarryThePenguin/no-unused-prop-types-in-jsx3b25a3bMerge pull request #882 from kentor/jsx-max-props-per-line-updatesThere are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.