You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In violation parsing, violations can be grouped by rule.
The description used is the one from the first violation that is parsed. The message can be different for every violation.
Currently some rules put different descriptions for the same violation identifier (possibly resulting in wrongly parsed violations in the output)
Probably best to have an enum with the identifier and description for each rule, and use that in the violation creation. And update the rules to use the message property in the violation object to differentiate different kind of violations within the same rule.
The text was updated successfully, but these errors were encountered:
In violation parsing, violations can be grouped by rule.
The description used is the one from the first violation that is parsed. The message can be different for every violation.
Currently some rules put different descriptions for the same violation identifier (possibly resulting in wrongly parsed violations in the output)
Probably best to have an enum with the identifier and description for each rule, and use that in the violation creation. And update the rules to use the message property in the violation object to differentiate different kind of violations within the same rule.
The text was updated successfully, but these errors were encountered: