#731 #732 Scope of "extends" and "superClass" directives in VPDSL #736
+18
−11
Conversation
This file contains 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
|
Kudos, SonarCloud Quality Gate passed! |
pdulth
force-pushed
the
master
branch
2 times, most recently
from
8910bb8
to
9b704ad
Compare
…cope to all superClasses and all their extends
etraisnel2
force-pushed
the
731-732-scope-extended
branch
from
1008cad
to
ac5f0e3
Compare
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.
getExtendedElement now properly extends the scope to all superClasses and all their extends
#734 should be merged first to ensure that no viewpoint is considered wrongly considered active
This can cause childCreationExtenders to be used where they shouldn't