Fixed Bug with Collapse/Expand All Tree Groups #4178
Merged
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.
This PR fixes the inconsistencies when collapsing/expanding all tree groups or sub-groups introduced by PR #4143. See issue description: #4162
It looks like the expansion state of each node/group is saved in two different places:
node
itself:node.expanded
As far as I can tell, adding
expandedGroupIds
to thesetExpansionOfAllSubgroupsTo
solves this issue.URL of deployed dev instance (used for testing):
Steps to test:
Issues: