fix/COMPASS-9956 use more stable key for field component rendering #154
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.
External Links
Description
When index is being used as a key and a field is removed from the list, react keeps the elemet around with incorrect state (see before / after)
Notes for Reviewers
I don't see any tests for node field updating, so not sure where to add one, but it would be good to merge the fix to get it to compass as this is affecting field editing and expand collapse a lot
📸 Screenshots/Screencasts
Before
After