-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Fixed wrapped inputs with non-string values & checkboxes #129
Conversation
@tonsky The tests are failing. Also,
I think I would prefer the second approach. What do you think? |
Yeah, I’ve seen the tests. Turned out we were still using wrapped inputs for uncontrolled components. When I fix that, it turned out that we can’t use native inputs because of value=nil in props :( |
Ok, I think I’ve fixed that. Tests pass, I returned single |
@tonsky Thanks! Let me check it on one of my projects, then I'll merge it and cut a release. |
@tonsky Ok, released as |
Awesome! Thanks a lot On Wed, Aug 17, 2016 at 3:48 PM r0man [email protected] wrote:
|
Hey, I noticed you’re from Berlin, right? Wanna meet tomorrow? I’ll be there https://twitter.com/nikitonsky/status/766897501534162944 |
Hey Nikita, On 20 Aug 2016 09:25, "Nikita Prokopov" [email protected] wrote:
|
First, 579f3d7 introduced a bug when inputs which have non-string
:value
were unable to update. Two people reported that, I hit that too, and that patch resolves that by coercingprops.value
to string before storing it intostate_value
.Second, I just realized that
wrapped-form-element
won’t work properly for checkboxes and radio buttons, because they usechecked
instead ofvalue
. But they havevalue
as well, it just mean different thing for them. So there’s new branch for wrapping checkboxes/radio buttons now