From ce082c76f6fe5bd4428647bf3268d2c76c3c18f9 Mon Sep 17 00:00:00 2001
From: "detail-app[bot]" <180357370+detail-app[bot]@users.noreply.github.com>
Date: Sun, 6 Sep 2026 23:51:27 +0000
Subject: [PATCH] docs: correct no-duplicate-string severity after i18n-aware
 rule split

---
 docs/ui-code-quality-gate.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/ui-code-quality-gate.md b/docs/ui-code-quality-gate.md
index c7a7b81e6729..f8e3f6f75cdc 100644
--- a/docs/ui-code-quality-gate.md
+++ b/docs/ui-code-quality-gate.md
@@ -175,7 +175,9 @@ that already runs on every UI PR. A finding in your editor is the finding Sonar
 
 The high-backlog SonarJS rules are also enforced *blockingly* by SonarCloud, whose Clean-as-You-Code
 model scopes them to **new lines** — something ESLint fundamentally cannot express. So
-`cognitive-complexity` and `no-duplicate-string` warn locally and block on new code in the PR gate.
+`cognitive-complexity` warns locally and blocks on new code in the PR gate. The stock
+`sonarjs/no-duplicate-string` is `off` because it flags i18n keys (`t('label.…')`) that must stay
+inline; the i18n-aware `openmetadata-i18n/no-duplicate-string` replacement is enforced at `error`.
 
 `eslint-plugin-sonarjs` is pinned **exactly** (`4.2.0`). SonarCloud upgrades its analyzer server-side
 on its own schedule and that drift is silent.