🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
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.
Hello lovely humans,
eslint-plugin-react just published its new version 7.0.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 :sparkles:
You rock!
:palm_tree:
GitHub Release
Fixed
jsx-curly-spacingallowMultilineoption being undefined in some cases (#1179 @fatfisz)jsx-curly-spacingnewline with object literals bug (#1180 @fatfisz)prop-typesto not mark class static function as valid propTypes definition (#1174)prop-typescrash with Flow spread operator (#1178)void-dom-elements-no-childrencrash on faultycreateElementdetection (#1101)require-default-propserror message for quoted props (#1161)Changed
The new version differs by 457 commits .
7ca9841Update CHANGELOG and bump version9ce4d85Merge pull request #1192 from markus-willems/pr/prop-types-docs660790bfix for wrong rule syntax. no-unused-prop-types instead of react/no-unused-prop-types in docs227fcf3fix for wrong rule syntax. prop-types instead of react/prop-types in docsaf68f88Fix require-default-props error message for quoted props (fixes #1161)f7fb96bFix void-dom-elements-no-children crash on faulty createElement detection (fixes #1101)f111e45Merge pull request #1180 from fatfisz/fix-newline-with-object-literals3743e6dAdd additional test with flow annotations to prop-types1ced710Fix no-unused-prop-types crash with Flow spread operator (fixes #11781534bdbFix the newline with object literals bug159d0e5Update rules to match changes in comments attachement in ESLint 4.0.01b5743fUpdate tests to pass parserOptions globally0a2c510Fix indent errors1bcaee0Update .eslintrc config for ESLint 4.0.0dd10133Fix prop-types crash with Flow spread operator (fixes #1178)There are 250 commits in total. See the full diff.