-
Notifications
You must be signed in to change notification settings - Fork 49
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
callable types unhandled? #26
Comments
That warning is in how you're using |
hmmm, here's a gist (I'm working on an integration with react-formal): https://gist.github.com/rosskevin/e166b1a174f961ac61a091930dfcefa7 Do you spot the misuse? |
maybe related: reduxjs/react-redux#6 es7 use? |
You're not specifying an onChange or onBlur here: https://gist.github.com/rosskevin/e166b1a174f961ac61a091930dfcefa7#file-signin-js-L71 |
That's a react-formal Effectively: <Field>
<TextField {...this.props} onChange={x} onBlur={x} />
</Field> |
Right. But you never pass those props to There's nothing in here: https://github.com/jquense/react-formal/blob/master/src/Field.jsx that's going to pass an |
Maybe I'm not describing it well. I don't want to/intend to pass these handlers...ever. react-formal I know with certainty that Here (my I don't spot |
Ah, didn't realize it was context aware to the And no, propTypes are runtime checks. There's nothing static about them/no guarantees of any kind, so if you're getting a warning from them (as you are here), the warning is indicating a specific example of a runtime type check (in this case, your |
Ok, thanks much for the look, helps my understanding. I'll figure out where/when/why it is missing, certainly if the check is implemented, it's a good warning! |
I receive
Warning: Failed propType: Required prop onBlur was not specified in TextField.
This flow code:
Generates:
The
onChange
andonBlur
are specified, not null, and of the signature I have specified.Am I missing something or is this not yet supported?
The text was updated successfully, but these errors were encountered: