Skip to content

Solve flow issues on v0.29.1 #8773

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

Closed
techmentormaria opened this issue Jul 14, 2016 · 7 comments
Closed

Solve flow issues on v0.29.1 #8773

techmentormaria opened this issue Jul 14, 2016 · 7 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@techmentormaria
Copy link

When I run flow on v0.29.1 I get many errors. This happened to me with a few other RN versions now as well. Can you make sure to check flow before pushing to master? It's pain

That may happen to me because I'm using the newest flow version (0.28.0) and not the recommended version(0.25.0 as seen in .flowconfig). Can you please check that as well?

Thanks!

@satya164
Copy link
Contributor

@mhollweck It would be great if you can send a PR to fix flow issues.

@dozoisch
Copy link
Contributor

@mhollweck If you do a fresh react-native init with [email protected] you should see [email protected] as recommended version in flowconfig.

@jawang35
Copy link

I'm getting a lot of flow errors on [email protected] with [email protected] as well and I changed the version in the flowconfig to 0.28.0. The errors disappear if I use 0.27.0 and change the flowconfig to match that version.

@frostney
Copy link
Contributor

I ran into the same problem and @jawang35's workaround with using Flow 0.27 worked for me as well.
As far as I can tell some of the flow errors are happening because of the updates to unions and intersections that have been implemented with Flow 0.28 (https://flowtype.org/blog/2016/07/01/New-Unions-Intersections.html). The definitions in NavigationExperimental in RN 0.29.x don't cater to that. That being said, I've noticed that the flow errors related to unions are solved in master.

@ide
Copy link
Contributor

ide commented Jul 20, 2016

The unit tests do run Flow, so if the Flow checks fail on master we'll see red X's right away.

@fantattitude
Copy link

fantattitude commented Aug 2, 2016

React-Native 0.30.0 have a flow version of ^0.27.0 in its .flowconfig so I guess somebody realized there was a problem ?

@hramos
Copy link
Contributor

hramos commented Nov 1, 2016

Seems like this can be closed now, ping me if you believe otherwise.

@hramos hramos closed this as completed Nov 1, 2016
@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

9 participants