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
'smessage
field. https://github.com/tomasbjerre/violations-lib/blob/e083e670887819141279f2c11fcedc042a50245a/src/main/java/se/bjurr/violations/lib/parsers/FindbugsParser.java#L73These 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 toViolation
.This would facilitate emitting the details in a more appropriate output field; for instance, in the CodeClimate's content field.