Fix move/swap breaking input fields #16
Merged
+145
−25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
During move and swap, the field state of the source field was copied to the target field. The field state, however, contained functions that had a reference to the previous position. This caused changes to be applied to the wrong field. Resolves: final-form#15 See also: final-form#10
Codecov Report
@@ Coverage Diff @@
## master #16 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 9 9
Lines 82 84 +2
Branches 16 16
=====================================
+ Hits 82 84 +2
Continue to review full report at Codecov.
|
|
Can someone merge this, pls? |
|
Published in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
During move and swap, the field state of the source field was copied to
the target field. The field state, however, contained functions that had
a reference to the previous position. This caused changes to be applied
to the wrong field.
Resolves: #15
See also: #10