-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
no-unused-prop-types fails on readonly flow types #1388
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
What version of flow are you using? |
This error is occurring for us internally at Facebook, we are on latest.
|
Confirmed the bug. Will fix it! @TheSavior are there any other such syntax that we could test? My fix should tackle all kinds of prefixes, but better save than sorry. I see there is also a |
I'm not sure, I'll run this rule through our codebase and flag all of the places that it seems to have false positives. That should give a pretty good signal. |
@jseminck there's covariant (+) and contravariant (-), at least |
If your Props type definition is:
The rule will provide the warnings:
The text was updated successfully, but these errors were encountered: