You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I initially raised #650 because I had many components not reporting display-name issues when being assigned directly to module.exports (and ending up with 'exports' as the name in the devtools).
I've since done some for investivation and narrowed it down to using React.createClass() passing in an object containing an ES6-style method.
This does not report an error for "react/display-name": "error"
Further, it has something to do with the method() property having its own 'name', not the whole class, as this also does not trigger the display-name error:
I initially raised #650 because I had many components not reporting display-name issues when being assigned directly to module.exports (and ending up with 'exports' as the name in the devtools).
I've since done some for investivation and narrowed it down to using React.createClass() passing in an object containing an ES6-style method.
This does not report an error for
"react/display-name": "error"
or even:
Further, it has something to do with the method() property having its own 'name', not the whole class, as this also does not trigger the display-name error:
and
eslint-pluign-react: "6.2.2"
example repo peet/display-name-test
The text was updated successfully, but these errors were encountered: