SonarQube properties documentation should indicate expected file format for StyleLint report

[CrushaKRool]

The documentation page Importing third-party issues lists the available properties for importing external reports.

For some reports, it explicitly states whether you need to use a specific formatter and how to configure it. E.g. for TypeScript:

Comma-delimited list of paths to TSLint reports in JSON format (use -t json TSLint option)

However, for CSS it only says:

Comma-delimited list of paths to StyleLint.io reports

But when using the default file output of the StyleLint CLI, you get a human-readable format like

src/sass/_globals.scss
  34:4  ✖  Unexpected unit  length-zero-no-unit

that SonarQube cannot parse.

You actually need to use the --formatter json argument in the CLI command to get it to produce the right report. This should be amended in the documentation.

[tony.briget]

Hi @CrushaKRool,

Thanks for raising this. We appreciate your contribution. We’ve created a documentation ticket internally and we’ll update this section.

Have a great day,

Tony