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
The endpoint should be improved to return also at least a boolean to indicate whether a rule violation has been resolved, to that the could only show unresolved rule violations, or pre-configure a UI filter accordingly.
Maybe some additional information about a rule violation resolution would be nice, like the place where it's configured. So instead of a boolean, there could be a ResolutionType enum saying UNRESOLVED, RESOLVED_BY_REPO_CONFIG, etc.
The text was updated successfully, but these errors were encountered:
sschuberth
changed the title
Improve the rule violations endpoint to take resolved resolutins into account
Improve the rule violations endpoint to take resolved resolutions into account
Feb 21, 2025
sschuberth
changed the title
Improve the rule violations endpoint to take resolved resolutions into account
Improve the rule violations endpoint to take resolutions into account
Feb 21, 2025
Currently, https://eclipse-apoapsis.github.io/ort-server/api/get-rule-violations-by-run-id seems to always return all rule violations, independently whether they have already been resolved, e.g. via an
.ort.yml
rule violation resolution, or not.The endpoint should be improved to return also at least a boolean to indicate whether a rule violation has been resolved, to that the could only show unresolved rule violations, or pre-configure a UI filter accordingly.
Maybe some additional information about a rule violation resolution would be nice, like the place where it's configured. So instead of a boolean, there could be a
ResolutionType
enum sayingUNRESOLVED
,RESOLVED_BY_REPO_CONFIG
, etc.The text was updated successfully, but these errors were encountered: