Suppress issue in C++ source file

I understand your frustration @Matthias.Guelck. We looked at the problem recently and right now the direction we will be taking will be to:

  • deprecate the use of //NOSONAR alone
  • request a RuleKey (or multiple keys) to be provided like “//NOSONAR(S123, S222, …) Justification” => very similar to @SuppressWarnings(“squid:S…) but more language agnostic
  • automatically Open and Close as Won’t Fix issues that are silenced by this mechanism for traceability purpose

Would that work for you?

1 Like