-
Notifications
You must be signed in to change notification settings - Fork 649
onChange doesn't fire when form type is array #295
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
Comments
Fixed, closing. |
This is not fixed, the pull request in #374 has not been merged. |
I believe this is fixed in the latest updates (alphas) for the eventual 1.0.0 release. Please re-open if there are still issues in these versions. |
Hmmm the test case in the originally proposed PR fails, re-opening just in case it isn't fixed. |
Nope just fixed the test and it does pass. All good. |
Hi Team, In which version of release this patch is available. I am using bower to install and after running bower install. the patch code mentioned in this case(i.e onChange for array) is not available. Please, let me know what I have do to get patch through bower. Thanks, |
@santhoslokanath as mentioned above it is fixed in the alphas, it is not in a release yet, I suggest using npm and pulling the alpha version. Bower won't be supported much longer I expect as they recommend using yarn on their own homepage https://bower.io/ |
As the title says, if I add an onChange handler to an array field, and then add or remove an item to that array, the handler doesn't fire.
The text was updated successfully, but these errors were encountered: