You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: i18n support for the dashboard UI
Problem
The dashboard (ui/) is English-only. Teams whose operators use other languages have to fork the UI to localize it, which makes every upstream release a large merge.
Current state on dograh-v1.49.0:
No i18n library or message catalogs. UI strings are inline across about 244 .tsx files.
<html lang="en"> is fixed (ui/src/app/layout.tsx:53).
Dates are hard-coded to en-US (ui/src/lib/dateTime.ts:8,20, ui/src/lib/billingFilters.ts:26), and the calendar has no locale (ui/src/components/ui/calendar.tsx).
API errors are English sentences in detail (about 160 in api/routes/), and some pages display them as-is.
Proposal
Add an i18n library that works with the App Router (e.g. next-intl), with per-locale message catalogs split by feature.
Format dates, calendars and numbers with the active locale; set <html lang> to match.
Move UI strings into catalogs page by page, and add a lint rule that blocks new hard-coded strings.
Have the API return stable error codes alongside detail, so the UI can translate them. This can be a separate issue.
Acceptance criteria
Adding a language only requires adding a catalog.
English behaviour is unchanged.
CI fails when a new hard-coded user-visible string is added.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Feature request: i18n support for the dashboard UI
Problem
The dashboard (
ui/) is English-only. Teams whose operators use other languages have to fork the UI to localize it, which makes every upstream release a large merge.Current state on
dograh-v1.49.0:.tsxfiles.<html lang="en">is fixed (ui/src/app/layout.tsx:53).en-US(ui/src/lib/dateTime.ts:8,20,ui/src/lib/billingFilters.ts:26), and the calendar has no locale (ui/src/components/ui/calendar.tsx).detail(about 160 inapi/routes/), and some pages display them as-is.Proposal
next-intl), with per-locale message catalogs split by feature.<html lang>to match.detail, so the UI can translate them. This can be a separate issue.Acceptance criteria
All reactions