-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
jsx-no-bind
errors on non-react components.
#663
Labels
Comments
petersendidit
added a commit
to petersendidit/eslint-plugin-react
that referenced
this issue
Jul 12, 2016
petersendidit
added a commit
to petersendidit/eslint-plugin-react
that referenced
this issue
Jul 12, 2016
JSX (Fixes jsx-eslint#663) Enhance isReturningJSX to handle more node types
petersendidit
added a commit
to petersendidit/eslint-plugin-react
that referenced
this issue
Jul 13, 2016
JSX (Fixes jsx-eslint#663) Enhance isReturningJSX to handle more node types
yannickcr
pushed a commit
that referenced
this issue
Jul 14, 2016
@yannickcr can you bump the alpha? (or better, the major :-) ) |
@ljharb I just published |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have Backbone views with a "render" method that are being warned when they have
.bind
used within them. Did something change recently that loosened the criteria for identifying a React component?If the
render
method doesn't return JSX, and the component doesn'textend React.Component
, and most importantly if the file itself doesn't even import/requireReact
, why are these rules applying to it?The text was updated successfully, but these errors were encountered: