In the FindbugsParser, the details of the bug is being included in the Violation's message field.
|
messagesPerType.put(type, shortDescription + "\n\n" + details); |
These messages can be very long, and also include HTML formatting. When viewing the report in GitLab (from a CodeClimate output) the message is difficult to read, and badly formatted.
Instead of including the details in the message field, the specifics map could be used. Or perhaps a new field added to Violation.
This would facilitate emitting the details in a more appropriate output field; for instance, in the CodeClimate's content field.
In the FindbugsParser, the details of the bug is being included in the
Violation'smessagefield.violations-lib/src/main/java/se/bjurr/violations/lib/parsers/FindbugsParser.java
Line 73 in e083e67
These messages can be very long, and also include HTML formatting. When viewing the report in GitLab (from a CodeClimate output) the message is difficult to read, and badly formatted.
Instead of including the details in the message field, the
specificsmap could be used. Or perhaps a new field added toViolation.This would facilitate emitting the details in a more appropriate output field; for instance, in the CodeClimate's content field.