We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using flow typings and I noticed this error after running script prefixing deprecated lifecycle methods. Basic example:
type Props = { dataDirty: boolean }; class RandomComponent extends Component<Props> { UNSAFE_componentWillReceiveProps(nextProps: Props) { if (nextProps.dataDirty) { doSomething(); } } }
this triggers 'dataDirty' PropType is defined but prop is never used. When UNSAFE_ prefix is removed the error is gone.
'dataDirty' PropType is defined but prop is never used
edit: it might be worth to mention, when searching I found this old issue: #884 But in my case destructuring the nextProps didn't fix the error
The text was updated successfully, but these errors were encountered:
Issue seems to be gone after updating eslint
Sorry, something went wrong.
No branches or pull requests
I'm using flow typings and I noticed this error after running script prefixing deprecated lifecycle methods. Basic example:
this triggers
'dataDirty' PropType is defined but prop is never used
. When UNSAFE_ prefix is removed the error is gone.edit: it might be worth to mention, when searching I found this old issue:
#884
But in my case destructuring the nextProps didn't fix the error
The text was updated successfully, but these errors were encountered: