-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Report error which Flow does not report #71
Comments
Not sure what C/C++ has to do with flow. Can you please elaborate on this. Is there a feature of C that you want in flow? |
Not at all. I'd just like Again, Flow says |
@pizzafroide would be great if you could make a PR for this |
@amilajack I'm a little busy right now and have no time to address this issue. For now, I've just added a note telling that this kind of error is actually OK. But I'll consider making a proper PR later on. Thanks for the links to the related issues anyway. |
It is an issue with flow. Not sure if we can find a work around... |
Closing this, as we're waiting on flow. @jdmota Thanks for finding this! |
Hi, It's been more than a year since the issue was reported to Flow and it is still open. I understand that the first purpose was to save processing time by running Flow on only one file. But the Flow process is actually blazingly fast, so wouldn't it be conceivable to spawn the Flow process once at the start of the eslint process, then filter the output for each file ? I tried to run Flow without the This would solve the issue at stake here. The difference I see is that we are letting Flow reading the content of the file from the filesystem, instead of feeding it from What is your opinion @amilajack ? |
Another year has gone by, and I'm still running into this issue. I've resorted to sticking |
This use case is where, in C/C++, a forward declaration would be needed.
A.js
:B.js
:Flow says
No errors!
butflowtype-errors/show-errors
reports the following inA.js
:The text was updated successfully, but these errors were encountered: