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 6.4.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 :sparkles:
You rock!
:palm_tree:
GitHub Release
Added
skipUndeclaredoption toprop-types(#846 @pfhayes)Fixed
jsx-no-bindcrash on arrow functions (#854)display-namefalse negative on es6-style method inReact.createClass(#852)prefer-stateless-functionto allow components withchildContextTypes(#853)no-children-propspread support (#862 @randycoulman)no-unused-prop-typesto ignore validation when spread is used (#840)jsx-closing-bracket-locationfor multi-line prop (#889)jsx-indentin multi-line function calls (#895)jsx-indentin multi-line logical expressions (#540)Changed
The new version differs by 150 commits .
608c14aUpdate CHANGELOG and bump version29de657Update dependencies963267aFix jsx-indent in multi-line logical expressions (fixes #540)1e1c5c6Fix jsx-indent in multi-line function calls (fixes #895)e2f72f1Fix jsx-closing-bracket-location for multi-line prop (fixes #889)a1b8d45Add ES6 import example to "jsx in scope" docsfc7b02aMerge pull request #876 from manovotny/patch-1ac548a0Adds missing rule name forjsx-no-bind.b464cf1Add skipUndeclared option to prop-types rulecc39fb8Merge pull request #830 from eelyafi/jsx_indent_fixer90af71bAdded note to the docs3f393a2Fix no-unused-prop-types to ignore validation when spread is used (fixes #840)f227eb4Fix no-children-prop spread support2adefb7Merge pull request #863 from corydolphin/patch-10fa8c76Fixes incorrect grammar in react/prefer-stateless-function docsThere are 150 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade