-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Flow types: intersecting inexact shape types is too buggy, causes errors in userland with more recent versions of flow #151
Comments
jedwards1211
changed the title
Flow types: intersecting inexact shape types just doesn't work
Flow types: intersecting inexact shape types just doesn't work and causes errors in userland
Sep 17, 2020
jedwards1211
changed the title
Flow types: intersecting inexact shape types just doesn't work and causes errors in userland
Flow types: intersecting inexact shape types just doesn't work, and causes errors in userland
Sep 17, 2020
jedwards1211
changed the title
Flow types: intersecting inexact shape types just doesn't work, and causes errors in userland
Flow types: intersecting inexact shape types is too buggy, causes errors in userland
Sep 17, 2020
Also the |
jedwards1211
changed the title
Flow types: intersecting inexact shape types is too buggy, causes errors in userland
Flow types: intersecting inexact shape types is too buggy, causes errors in userland with more recent versions of flow
Sep 17, 2020
The solution for me was to downgrade from 3.1.3 to 3.1.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Let me know if you want a PR...I think we need to investigate workarounds before we proceed...
I'm getting errors like this:
Problem is here:
react-final-form-arrays/src/types.js.flow
Line 57 in 16f19c5
Intersecting inexact shape types in Flow has always caused problems like this sporadically.
It seems like this appears to work, though I don't trust it until I've played with it more:
I don't trust it until I've played with it more though, because I remember seeing inexact spreads like
{ name: string, ...UseFieldArrayConfig }
produce buggy errors (facebook/flow#1326 (comment)).The text was updated successfully, but these errors were encountered: