-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Why are the ...rest
properties not included in input
#10
Comments
The reason is that this library is just a wrapper for To accomplish what you're asking for would require React Final Form to provide some sort of optional |
I see!, so basically if I was to use the standard react-final-form Field in a same way as in the code above, the props Okay, that's an implementation detail I wasn't aware of, I thought that all input's applicable properties are passed in the input prop. Anyway, what you say makes perfect sense, thanks for clarification. |
it would be good to fix this |
While investigating another issue, I discovered that https://codesandbox.io/s/wqrywv2lkw
|
One does not simply do this as usually:
It is now necessary to also pass
({input, ...rest})
to<input {...input} {...rest}/>
, but careful, there also is themeta
object!, so we must first consume it even though we don't need it.({input, meta, ...rest})
I believe that it would make better sense to include all input props inside
input
property. If not, can you please shed some light on it and perhaps better documented in the example here? https://github.com/final-form/react-final-form-html5-validationThe text was updated successfully, but these errors were encountered: