Repository navigation
fix(ontology): cardinality of one can be added to classes as long as not used in data - #1958
Merged
Merged
Conversation
BalduinLandolt
approved these changes
Dec 7, 2021
mpro7
approved these changes
Dec 8, 2021
subotic
approved these changes
Dec 10, 2021
|
Kudos, SonarCloud Quality Gate passed!
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
resolves DEV-233
It is now possible to add a cardinality to a class even if it has a subclass. This is only allowed if that class or any sub-class (recursively) is not yet used in data, i.e. has no resource instantiated from it. Therefore I added a new check
isClassUsedInData.