A scan reported a TODO code smell where there is not. Looking carrefully it was identified on the portuguese word “método” on a comment on a TypeScript file. My guess is that it is because the “é” character not being ASCII.
This was detected by SonarScanner 184.108.40.2062 (sonarsource/sonar-scanner-cli:latest) on my CI to SonarCloud. The sonar-project.properties file includes a
Thank your for your feedback, and welcome to the SonarSource community!
As you rightfully pointed out, the rule triggers an issue because é is not an ASCII character. In fact, the rule currently ignores todo occurrences iff it is surrounded by a character accepted by the regular expression [A-Za-z]. This is incorrect as the rule could reports false-positives, which happens to be the case with your example.
I created this ticket to address this issue as soon as possible.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.