Fix: Set Constraints without objects are not evaluated #118
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
Refactoring validateSetConstraint
- Enables evaluation of Constraints without corresponding objects in allObjects - Avoid multiple logs of same error log when configured log message is available. - Evaluate SET Constraints on SET not each element.
- Evaluate polygons under test successively - Reuse duplicated code
- SET CONSTRAINTS may not operate on individual elements (use Mandatory constraints on Objects) - Update test expectations.
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.
TODOs:
>MyClassmay not be evaluated correctly. (evaluateObjectCount)SET CONSTRAINTsSET CONSTRAINTdo not reference singular attributes / objects