Elena Vilchik

Another similar problem https://community.sonarsource.com/t/specifying-sonar-exclusions-for-folder-that-begins-with-a-dot/62101

https://sonarsource.atlassian.net/browse/MMF-2926

@agigleux could you confirm if this ticket makes sense?

Reported in https://community.sonarsource.com/t/eslint-report-import-all-issues-have-the-same-severity/62084/4

IMO `case Target.World: str += ", our awesome world!"; break;` is unreadable and should not be ignored by the rule I think disabling this particular lines (if you are so...

@DaFri-Nochiterov indeed your screenshot is readable, thanks to highlighting and homogeneous code. I would agree on making `break` inside `case` excluded based on config. But not every kind of statement

Thanks for idea, we will consider it when doing next sprint

@slubowsky thanks for the feedback. Sounds reasonable! ``` function foo(p1: number, _p2?: boolean) { // '_p2' should not be reported as it unused return p1 * 2; } ``` When...

@mum-viadee thanks for the request. We will think about it. Do you already see any way for us to do it? There is `ruleSeverity` property available for each issue (`error`...

@xxluke I don't think we want to consider tslint disable comments in SonarQube In your use-case, if you really want to use TSLint, I would suggest to have an empty...