-
Notifications
You must be signed in to change notification settings - Fork 77
Add ReportQuery objects to Report #879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This fails with:
... but it passes locally. I'm wondering if there's some sort of ordering difference in each report query? I sorted the report queries by name, but maybe the actual violations within each report query are getting sorted different. Any ideas? We could sort these, but the Violation objects are kind of complex and we couldn't sort until rendering, which might get messy... |
Without using To resolve this, I changed the diffing of TSV files in |
I think changing CommandLineIT is a good solution. I'll take one more look at the code tomorrow. Thanks! |
robot-core/src/main/java/org/obolibrary/robot/ReportOperation.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All right, let's just do this.
This is an alternative to #875 that allows us more flexibility in the future. Resolves #871.
docs/
have been added/updatedmvn verify
says all tests passmvn site
says all JavaDocs correctCHANGELOG.md
has been updatedThis adds a new
ReportQuery
object that carries the details of the "rules" including rule name, query contents, violation level, a list of the found violations, and an optional URL for documentation. If you are generating an HTML report, the default report queries will have links to their documentation.