Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, @erikras!
Sorry for directly mentioning you, but I need your help!
I opened issue #19 some time ago, and since there were no activities, I tried to handle it myself.
It turns out that the bug occurs due to
moveFieldState
function, which expects that objects in the array have the same shape. It's not always true. I wrote a test for this case.I will be glad to make a fix, but I not sure what to do with these
change
,blur
andfocus
handlers in case if there is nostate.fields[destKey]
field.Could you tell the right way to handle this?