Remove both owner and memberNamespace in model browser #2989
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
So there's no lingering elements around.
3 tasks
danyeaw
approved these changes
Jan 7, 2024
There was a problem hiding this comment.
Thanks @amolenaar, I have just been recently creating new Stereotypes and I can make use of this fix immediately 👍
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.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When creating a stereotype, a ghost/rogue element appears at the root of the model browser.
Issue Number: #2987
What is the new behavior?
When removing an element, remove it both from the
ownerand from thememberNamespacebranches in the model browser.Does this PR introduce a breaking change?
Other information