-
Notifications
You must be signed in to change notification settings - Fork 200
Flow errors #87
Comments
Issue #86 is about the same thing I think |
thanks @kpyorala - I haven't run this on 0.32 yet, that's a tricky thing about Flow -- hard to keep up with versions! could you possibly submit a PR to fix these and update us to 0.32? |
We have experienced this issue internally and I am working on a fix today. Will send over a pull request updating to latest Flow. |
If you are fixing this can you also make sure anywhere the code specifies a react component for a prop it uses the type React.Element<*>. That way the prop types will propagate correctly. Many places it is ReactElement<{}> which breaks prop type checking. |
Hi, I'm also running flow (version 0.33.0) on a project using ex-navigation and I'm getting a lot of flow errors from inside of ex-navigation (version 2.1.3). I understand if the errors are hard to fix, but is there anything I can add to my
|
Any ETA on this? 😃 |
I am also running into this issue with flow version 0.35.0. I also got the following errors:
I was able to ignore the errors by adding the following to my
Note with this solution you need to force flow to ignore any imports from
Are you still working on this @grabbou ? |
tl;dr use `flow-check` script to typecheck code. Add a babel plugin to strip out type declarations from resulting code, thus making it possible to actually write them and have things working afterwards. Also brings in `flow-result-checker`, an ugly workaround for facebook/flow#869 - the tl;dr is Flow reports type errors in all the `//@flow`'ed files, including ones in `node_modules` - which isn't entirely helpful. This affects us due to expo/ex-navigation#87, the tl;dr for which is ex-navigation has type errors and no one seems to be working on it ATM. So, code can currently be typechecked as mentioned at the top of the commit message; also, one of the components has been annotated to demonstrate.
I have Flow version 0.32.0 and ex-navigation version 1.5.26. When I run flow in my project root I got this:
Am I missing some configurations or what is the problem?
The text was updated successfully, but these errors were encountered: