Fixed wrapped inputs with non-string values & checkboxes#129
Fixed wrapped inputs with non-string values & checkboxes#129r0man merged 2 commits intor0man:masterfrom tonsky:master
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 notifications@github.com 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" notifications@github.com wrote:
|
First, 579f3d7 introduced a bug when inputs which have non-string
:valuewere unable to update. Two people reported that, I hit that too, and that patch resolves that by coercingprops.valueto string before storing it intostate_value.Second, I just realized that
wrapped-form-elementwon’t work properly for checkboxes and radio buttons, because they usecheckedinstead ofvalue. But they havevalueas well, it just mean different thing for them. So there’s new branch for wrapping checkboxes/radio buttons now