-
Notifications
You must be signed in to change notification settings - Fork 864
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
Add correct PersistGate defaultProps to support newer flow versions #974
Conversation
I only have a quick comment, correct me if I'm wrong please. You can provide a loading component or you can ignore it, so it's kind of "optional", I think this might be the reason it was set optional in the flow type? If that is the case, is there another solution to make it optional and get rid of the flow error? (maybe by providing a default value or something). Please let me know what do you think. |
Removing the |
And there seems to be no other option than removing the optional flag :/ |
Actually there is, I'll create a quick PR for that... |
Ops, looks like I don't have permissions to push a branch to the repo, what should I do? @erksch |
@aguynamedben Hey what's your status? I'd like to get this merged. I think many people can not update their flow version properly if this is not fixed. |
As mentioned in #953 there are type errors with some flow versions in the PersistGate component.
The problem with flow is described here:
facebook/flow#1660
A possible solution is described later in the issue and was already proposed by the creator of issue #953.
So what I did is adding
children: null
to the defaultProps and makingloading and children
not optional anymore.