feat(i18n): localize the Azure DevOps, Jira, Linear and Sentry task surfaces (#2284)
Co-authored-by: Kandev Agent <agent@kandev.dev> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -128,7 +128,15 @@ const NAMESPACE_RULES = [
|
||||
[/^(app|components)\/jira\//, "jira"],
|
||||
[/^(app|components)\/linear\//, "linear"],
|
||||
[/^components\/sentry\//, "sentry"],
|
||||
[/^(app|components)\/azure-devops\//, "azureDevops"],
|
||||
// `azuredevops`, not `azureDevops`: the shipped catalog is
|
||||
// `src/locales/en/azuredevops.json` and every existing reference is
|
||||
// `t("azuredevops:…")`. The camelCase form wrote a SECOND catalog file
|
||||
// beside the real one — verified by running this on
|
||||
// `azure-devops-work-item-detail.tsx`, which produced `azureDevops.json`
|
||||
// alongside `azuredevops.json`. Nothing would have failed: the new keys
|
||||
// resolve from the new namespace, so `i18n:check` stays green while the
|
||||
// directory's copy is split across two files.
|
||||
[/^(app|components)\/azure-devops\//, "azuredevops"],
|
||||
[/^components\/automations\//, "automations"],
|
||||
[/^components\/plugins\//, "plugins"],
|
||||
[/^components\/(integrations|vcs)\//, "integrations"],
|
||||
|
||||
Reference in New Issue
Block a user