-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
import/named doesn't detect Flow Opaque types in flow comments #921
Comments
Is this an issue only with flow comments? Possibly related to gajus/eslint-plugin-flowtype#260 ? |
Nope, I'm able to take off the flow comments and this error is still triggering a false-positive. |
@johnhaley81 I should notice that eslint couldn't track the flow stubs generated by flow-typed |
I have run locally the following test on current master (in the valid rules):
It is passing. Can we have a release? |
Closed by #1057, in that case. |
Hi all!
When using flow opaque types (new in https://github.com/facebook/flow/releases/tag/v0.51.0) via flow comments The
import/named
rule doesn't detect the exported types.Ex:
Foo.js
UseFoo.js
A weird workaround is to remove
makeFoo
fromFoo.js
and that will fix the linter rule. Don't know why that is. It's also not a good workaround since that makes the opaque type useless.The text was updated successfully, but these errors were encountered: