-
Notifications
You must be signed in to change notification settings - Fork 31
Update eslint-plugin-react to version 5.2.2 🚀 #524
Conversation
Autolander could not find a bug number in your pull request title. All pull requests should be in the format of: Bug [number] - [description]. |
32ea2ec
to
dfae93b
Compare
@Mardak What do you think about the bits that eslint complains about here? A bug in the plugin? |
70214da
to
b148185
Compare
b148185
to
04c2726
Compare
The change that caused the eslint test to fail: jsx-eslint/eslint-plugin-react#474 where previously it didn't look at the expressions. The jsx-no-bind rule is there to prevent each |
22000f8
to
2e82aa8
Compare
@@ -342,7 +342,7 @@ loop.roomViews = (function(mozL10n) { | |||
localPosterUrl={this.props.localPosterUrl} | |||
localSrcMediaElement={this.state.localSrcMediaElement} | |||
localVideoMuted={this.state.videoMuted} | |||
matchMedia={this.state.matchMedia || window.matchMedia.bind(window)} | |||
matchMedia={this.state.matchMedia || window.matchMedia} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So now you've done the nice changes, I'm not sure that matchMedia is actually used any more - looks like we dropped it at some stage. Maybe just drop it all now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, this is actually used on master.
r=Standard8 |
Hello lovely humans,
eslint-plugin-react just published its new version 5.2.2.
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-no-bind
crash (#641)The new version differs by 35 commits .
46c8008
Update CHANGELOG and bump version
281faf0
Fix jsx-no-bind crash (fixes #641)
d6d0d8a
Update CHANGELOG and bump version
ef406fa
Fix jsx-pascal-case for JSXMemberExpressions (fixes #637)
e626566
Update CHANGELOG and bump version
67053d9
Add missing no-comment-textnodes rule to README
698d7e5
Update dependencies
e341dfa
Fix prop-types crash when destructuring props with spread only
cd5ef2b
Integrate jsx-ast-utils
7586915
Fix jsx-curly-spacing alternative option
faaa823
Add support for ES7 bind operator to jsx-handler-names (fixes #630)
4418534
Add ignore option to no-unknown-property rule
2508576
Update README to add react/ prefix to rule names
0aeebaf
Fix sort-comp crash on spread operator (fixes #624)
aa359fb
Add no-comment-textnodes rule
There are 35 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade