Closed kaw2k closed 6 years ago
Going to use this issue as a vague roadmap so I don't forget 😄
fieldErrors
, etc) we would use that time to build a tree and store it to our instance (not state since it would be in the render function)onChange
function would need to tag each input with the id of the leaf of the tree it belongs to. This could cause performance hits on large trees as we would be generating new functions /shrugSince all of this would be happening on render, we would need to optimize this process quite a bit more than we are doing now. Still, the more I think about it the more feasible it is.
With making
normalizeInput
I can foresee a world where we forgoref
all together. We can still clone children and pass downonChange
(by convention) and enforce thatonChange
passes up the value of the input. Making the form tree would be trickier perhaps... I think we would get big wins in speed and maintainability. Also, I think the public API would remain largely unchanged. Will delay this until after v1 ships.