So first the property sonar.ts.tslintconfigpath belongs to Pablissimo’s ts plugin, so you won’t be able to use this on SonarCloud.
About sonar.typescript.tslint.reportPaths it seems to be correctly configured. But I need to verify if we still support that. Because, as I explained to you in a previous thread, SonarTS has been deprecated and is not used anymore on SonarCloud and I’m not sure if this setting is still supported by SonarJS. I’ll come back to you as soon as I have the answer.
And regarding tslint, you should know that it’s being deprecated and the tslint maintainers are working on eslint now instead. So you might want to import eslint reports instead of investing time into tslint.
Gregoire, thank you.
Yes, I remember your answer to my previous question.
But my customer already has tslint profile and asked me to integrate it to Sonar.
Than you both, I removed sonar.ts.tslintconfigpath from my Sonar scanner config. As for tslint report - by setting ‘max-line-length’ low into tslint.json I generated a lot of alerts in tslint report.
In general - should I see linter report under “Overview” section on the Sonar portal?
I don’t see any reason why TSLint issues might be missing from analysis I created a ticket to improve logging so that with next release of analyzer we will have more info -> https://github.com/SonarSource/SonarJS/issues/1840