Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update eslint-plugin-react to version 7.0.1 🚀 #95

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

greenkeeperio-bot
Copy link

🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrations first-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.


Hello lovely humans,

eslint-plugin-react just published its new version 7.0.1.

State Update 🚀
Dependency eslint-plugin-react
New version 7.0.1
Type devDependency

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

  • Fix jsx-curly-spacing allowMultiline option being undefined in some cases (#1179 @fatfisz)
  • Fix jsx-curly-spacing newline with object literals bug (#1180 @fatfisz)
  • Fix prop-types to not mark class static function as valid propTypes definition (#1174)
  • Fix prop-types crash with Flow spread operator (#1178)
  • Fix void-dom-elements-no-children crash on faulty createElement detection (#1101)
  • Fix require-default-props error message for quoted props (#1161)

Changed


The new version differs by 502 commits .

  • 7ca9841 Update CHANGELOG and bump version
  • 9ce4d85 Merge pull request #1192 from markus-willems/pr/prop-types-docs
  • 660790b fix for wrong rule syntax. no-unused-prop-types instead of react/no-unused-prop-types in docs
  • 227fcf3 fix for wrong rule syntax. prop-types instead of react/prop-types in docs
  • af68f88 Fix require-default-props error message for quoted props (fixes #1161)
  • f7fb96b Fix void-dom-elements-no-children crash on faulty createElement detection (fixes #1101)
  • f111e45 Merge pull request #1180 from fatfisz/fix-newline-with-object-literals
  • 3743e6d Add additional test with flow annotations to prop-types
  • 1ced710 Fix no-unused-prop-types crash with Flow spread operator (fixes #1178
  • 1534bdb Fix the newline with object literals bug
  • 159d0e5 Update rules to match changes in comments attachement in ESLint 4.0.0
  • 1b5743f Update tests to pass parserOptions globally
  • 0a2c510 Fix indent errors
  • 1bcaee0 Update .eslintrc config for ESLint 4.0.0
  • dd10133 Fix prop-types crash with Flow spread operator (fixes #1178)

There are 250 commits in total. See the full diff.

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants