# NOSONAR comment should be respected by SonarLint plugin in C++

**URL:** <https://community.sonarsource.com/t/nosonar-comment-should-be-respected-by-sonarlint-plugin-in-c/50603>\
**Category:** Suggest new features\
**Tags:** nosonar, cfamily, sonarqube-ide\
**Created:** [September 30, 2021, 8:14am UTC](https://community.sonarsource.com/t/nosonar-comment-should-be-respected-by-sonarlint-plugin-in-c/50603 "2021-09-30T08:14:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shojtsy](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@shojtsy](https://community.sonarsource.com/u/shojtsy)\
**Post date:** [September 30, 2021, 8:14am UTC](https://community.sonarsource.com/t/nosonar-comment-should-be-respected-by-sonarlint-plugin-in-c/50603/1 "2021-09-30T08:14:31Z")

</div>

SonarLint plugin running in standalone mode in Clion on C++17 code does not respect the // NOSONAR comment and still highlights issues in the same line.  
This makes it more difficult to focus on the real issues, they get buried under the false positives.

Environment: SonarLint 5.3.0.36775, Clion 2021.1.3, Ubuntu 20.04.3

---

<div class="post-metadata">

**Author:** ![Abbas](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/abbas/32/5717_2.png) [@Abbas](https://community.sonarsource.com/u/Abbas)\
**Post date:** [September 30, 2021, 10:26am UTC](https://community.sonarsource.com/t/nosonar-comment-should-be-respected-by-sonarlint-plugin-in-c/50603/5 "2021-09-30T10:26:50Z")

</div>

Hello @shojtsy,

You are right we don’t support NOSONAR in CLion yet. We are [working on it](https://jira.sonarsource.com/browse/CPP-3281).

Thanks,