Closed toddjordan closed 8 years ago
cc @samchrisinger
This is the approach I'm looking to take for issue #21. Still work in progress due to a mysterious phantomjs error I'm looking at, and I'm working on adding docs as well. Feel free to take a look though. I'm essentially just assigning a change handler on each field on the form, which will invoke the action. From the action you get the event object and can gain access to the field updated as well as other stuff int he form. I'll add an example in the docs. You can also look at the test for it too for usage.
Fixed the issue around phantom and added docs
This looks great!
@samchrisinger this pr has the action firing on change (which doesn't fire until you blur from the field). Which is preferable, on change or on keypress?
Keypress is much more useful to me.
Alright, I'll make an update to make that happen
@samchrisinger updated!
Thanks so much! This will be a huge help for us.
Addresses issue #21 Adding the ability for parent components to listen/react to changes in the form.
Allows the developer using dynamic forms to pass a closure action and have that action executed whenever a form field is changed.