From 9a0ad8e3827cf62a0cbefd67297346d3b1588815 Mon Sep 17 00:00:00 2001 From: Dorian Burihabwa <75226315+dorian-burihabwa-sonarsource@users.noreply.github.com> Date: Tue, 17 Dec 2024 11:55:14 +0100 Subject: [PATCH] SONARJAVA-5223 Fix unecessary language code in rule description (#4966) --- .../main/resources/org/sonar/l10n/java/rules/java/S2077.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S2077.html b/sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S2077.html index 64911293a30..6ab995608d8 100644 --- a/sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S2077.html +++ b/sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S2077.html @@ -1,5 +1,5 @@

Formatted SQL queries can be difficult to maintain, debug and can increase the risk of SQL injection when concatenating untrusted values into the -query. However, this rule doesn’t detect SQL injections (unlike rule {rule:java:S3649}), the goal is only to highlight complex/formatted queries.

+query. However, this rule doesn’t detect SQL injections (unlike rule {rule:javasecurity:S3649}), the goal is only to highlight complex/formatted queries.

Ask Yourself Whether