2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 18:08:03 +02:00
It can be useful to use in-code notation to suppress issues, but when those suppressions are no longer relevant they become a potential source of confusion and should be removed.
2023-05-03 11:06:20 +02:00
=== Noncompliant code example
2021-04-28 18:08:03 +02:00
2022-02-04 17:28:24 +01:00
[source,java]
2021-04-28 18:08:03 +02:00
----
@SuppressWarnings("squid:S4174") // Noncompliant
public void doSomething() {
final int LOCAL = 42; // S4174 is about naming of local constants but there's nothing wrong here
----
2023-05-03 11:06:20 +02:00
=== Compliant solution
2021-04-28 18:08:03 +02:00
2022-02-04 17:28:24 +01:00
[source,java]
2021-04-28 18:08:03 +02:00
----
public void doSomething() {
final int LOCAL = 42; // S4174 is about naming of local constants but there's nothing wrong here
----
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== Message
Remove this irrelevant "xxx", no such warning would be raised without it.
=== Highlighting
the suppression annotation/marking
2021-09-20 15:38:42 +02:00
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== is related to: S4632
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]