#11395: Fix TOC group is not restored in correct position when it has no direct child layer #11396
Conversation
This file contains hidden or 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
fix(TOC): ensure groups without direct layers are restored in correct position - Fixed an issue where newly created groups without direct child layers, but containing subgroups with layers, were not displayed in the correct position after saving - Added test cases to cover groups with only subgroups On behalf of DB Systel GmbH
congchen1101
changed the title
congchen1101
changed the title
1 task
tdipisa
added
bug
BackportNeeded
tdipisa
removed
the
BackportNeeded
tdipisa
added
the
BackportNeeded
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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 TOC groups without direct layers should be restored in correct position
On behalf of DB Systel GmbH
Description
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#11395
What is the new behavior?
Group without direct child layer is stored in correct position.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)