angular-i18n

Standard IDs

ID	Severity	What it checks
I18N-001	P1	Hardcoded UI strings with no i18n library wired
I18N-002	P1	Translation keys don't share a key space with the .NET DB-override table
I18N-003	P2	Dates/numbers/currency formatted with hardcoded locale instead of locale-aware
I18N-004	P2	No RTL layout support despite supporting a locale that requires it
I18N-005	P3	Locale switch requires a full page reload (advisory)

---

Check A — Hardcoded strings, no i18n library wired (I18N-001)

Detection

Grep templates for literal English text in labels/buttons/messages with no | translate pipe / i18n attribute / equivalent, and confirm a translation library (@angular/localize or a runtime library such as Transloco) is actually installed and configured. This is the same gap angular-dynamic-forms ADF-005 calls out for descriptor-driven forms — it applies to every other template too, not just dynamic forms.

BAD — hardcoded strings everywhere

<button>Approve</button>
<p>Your order has been confirmed.</p>

GOOD — every user-facing string resolved through the i18n pipe

<button>{{ 'orders.approve' | translate }}</button>
<p>{{ 'orders.confirmed' | translate }}</p>

---

Check B — Translation keys don't share a key space with the .NET DB-override table (I18N-002)

Detection

Compare the Angular translation key namespace against the .NET dotnet-localization DB-override table's Key column. If there's no documented shared convention (e.g., both sides use feature.subfeature.label dot-notation and the same key literally appears in both the Angular translation file and the DB override row for a shared string), an admin correcting a translation in the DB-backed override tool has no way to know whether it affects any given Angular string.

BAD — Angular and .NET translation keys evolved independently, no shared convention

// Angular: "customer_first_name"

-- .NET LocalizationOverrides table: Key = 'Customer.FirstNameLabel'
-- Same concept, no relationship between the two key strings.