-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
no-unused-prop-types: Potential regression introduced in 7.5.0 #1542
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
Comments
I'm still getting this error when passing an empty function as a default props.
I get this error:
Also, should I open this as a separate issue? ==> Opened a new issue #1581 |
Yes, please open a new issue. Thanks! |
I am still getting this issue in v7.5.1 see #1446 |
The error appears when you mistakenly define your propTypes,
instead of
or
|
I'm still getting this with v7.10.0, when using the this.setState(
state => ({
data: state.data.filter(({id}) => id !== authorization.id),
})
) |
@billyvg can you file a new issue, please? |
Hi there.
Noticed that my lint step failed after tagging my library with no code changes:
https://travis-ci.org/LINKIWI/react-elemental/builds/304035438
https://travis-ci.org/LINKIWI/react-elemental/builds/304036629
Interestingly, the failing build pulled in 7.5.0 of
eslint-plugin-react
which was published a couple minutes before the build kicked off.I haven't had time to do thorough investigation yet, but the 7.5.0 release seems to have introduced a regression in
no-unused-prop-types
:The text was updated successfully, but these errors were encountered: