fix relationship editor bug where deleting one relationship expanded the next relationship #1814
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.
Fix #1813
Description
Affected components
Related Issues
#1813
Solution and Design
Earlier, the
keyprop each element in the iterator was just the index of the array. This caused the state of the previous element to be passed down to the subsequent element after its deletion.The issue is fixed by making the relationship name as the key of the elements in iterator.
Steps to test and verify
Add multiple object/array relationships. Their expanded/collapsed state should be totally independent.
Limitations, known bugs & workarounds