Feat #1275 Made the rule Verificattion more user friendly by showing rows with violating things#1448
Merged
rdevoogtatstariongroup merged 2 commits intoJun 29, 2026
Conversation
rdevoogtatstariongroup
requested review from
lxatstariongroup and
samatstariongroup
June 25, 2026 12:42
samatstariongroup
requested changes
Jun 29, 2026
samatstariongroup
approved these changes
Jun 29, 2026
rdevoogtatstariongroup
force-pushed
the
feat/gh1275-UserFriendlyFeedbackRuleVerification
branch
from
June 29, 2026 14:23
12b1beb to
b9ac3ea
Compare
rdevoogtatstariongroup
deleted the
feat/gh1275-UserFriendlyFeedbackRuleVerification
branch
June 29, 2026 14:29
11 tasks
11 tasks
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
2 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.
Prerequisites
Description
Feat #1275
Rule violations now expand to show the violating model items, with a context-menu "Highlight" that flags them in both the Element Definition browser and the Product Tree.
The Status column now reflects the actual outcome: fixed RuleVerificationService so BuiltIn (and User) verifications persist PASSED/FAILED instead of always NONE via the write transaction instead of in-memory.
Also fixed non-persistent RuleViolations being wiped, so BuiltIn violations are finally shown