report-converter tool converts the output of an analyzer tool to plist format which is a common representation for CodeChecker commands. However, analyzers can print their results in different formats like json, plaintext, etc. Users need to read the documentation to get information about how to gather an output from these analyzers in a format that report-converter is able to consume. However, this documentation goes out of sync easily: https://github.com/Ericsson/codechecker/blob/master/docs/tools/report-converter.md
For example, at the time of this ticket's creation, Ruff parser section is missing. The solution to this problem could be extending the interface in report-converter so it is forced new parser creators to display the corresponding documentation to the users.
report-convertertool converts the output of an analyzer tool to plist format which is a common representation for CodeChecker commands. However, analyzers can print their results in different formats like json, plaintext, etc. Users need to read the documentation to get information about how to gather an output from these analyzers in a format thatreport-converteris able to consume. However, this documentation goes out of sync easily: https://github.com/Ericsson/codechecker/blob/master/docs/tools/report-converter.mdFor example, at the time of this ticket's creation, Ruff parser section is missing. The solution to this problem could be extending the interface in
report-converterso it is forced new parser creators to display the corresponding documentation to the users.