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

Prevent jsx-no-bind crash #1544

Merged
merged 1 commit into from
Nov 18, 2017
Merged

Prevent jsx-no-bind crash #1544

merged 1 commit into from
Nov 18, 2017

Conversation

jomasti
Copy link
Contributor

@jomasti jomasti commented Nov 18, 2017

The rule would assume a variable is initialized when checking a
VariableDeclarator node.

Fixes #1543

The rule would assume a variable is initialized when checking a
VariableDeclarator node.
@k1nger
Copy link

k1nger commented Nov 18, 2017

Tested and works on my environment.

@ljharb ljharb added the bug label Nov 18, 2017
@ljharb ljharb merged commit e0bae03 into jsx-eslint:master Nov 18, 2017
@ljharb
Copy link
Member

ljharb commented Nov 18, 2017

@yannickcr this, and #1545, should be released ASAP in a v7.5.1.

@jomasti jomasti deleted the issue-1543 branch November 18, 2017 21:40
@Andarist
Copy link
Contributor

Andarist commented Nov 18, 2017

Thanks for the quick fix! Although I'm not even sure how I got exposed to it 🤔 , considering that I have a yarn.lock with

eslint-plugin-react@^7.4.0:
  version "7.4.0"
  resolved "https://registry.yarnpkg.com/eslint-plugin-react/-/eslint-plugin-react-7.4.0.tgz#300a95861b9729c087d362dd64abcc351a74364a"
  dependencies:
    doctrine "^2.0.0"
    has "^1.0.1"
    jsx-ast-utils "^2.0.0"
    prop-types "^15.5.10"

@hadfieldn
Copy link

Just ran into this and came to see if there was a fix. Sure enough, less than 24 hours ago! Looking forward to 7.5.1. Thanks @jomasti !

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

Successfully merging this pull request may close these issues.

5 participants