BanManagement / BanManager-WebUI / 24628542846

72%

push

github

feat: add internationalization (i18n) support (#164) (#1765)

* feat: add internationalization (i18n) support (#164)

Introduces full i18n support using next-intl with English (en) and German
(de) catalogs, persistent per-user locale preference, locale-aware
formatting, and a standardised server-side error code system so messages
can be translated client-side.

Highlights:
- next-intl integration with deep-merged English fallback for missing keys
- LanguageSwitcher component + setLocale GraphQL mutation
- bm_web_users.locale column + persisting/loading user preference
- ExposedError now carries stable code + meta; surfaced via GraphQL
  formatError and Koa error middleware (BAD_USER_INPUT messages pass
  through verbatim per the documented out-of-scope policy)
- Locale-aware date formatting via dynamic date-fns locale loading with
  promise dedupe and eager default-locale preload
- Localised react-select and @nateradebaugh/react-datetime widgets
- Comprehensive message extraction across components, pages, notifications
- New server/data/error-translation.js shared by REST + GraphQL helpers
- Added unit tests: error-translation, formatError, locale helpers,
  setLocale mutation, me.locale field
- Documentation: README + CONTRIBUTING updates covering localisation
  workflow, adding new locales, and ExposedError compatibility note

* fix(i18n): preserve password length detail via INVALID_PASSWORD_LENGTH

The Cypress login error test expects "Invalid password, minimum length 6
characters", but with i18n the client looks up the error code in the
translation catalog. The shared INVALID_PASSWORD code mapped to the
generic "Password is invalid", losing the actionable length detail.

Split into two codes so the message stays specific without baking the
magic number into translations:

- INVALID_PASSWORD: kept generic ("Password is invalid"), used for the
  unreachable type-mismatch case.
- INVALID_PASSWORD_LENGTH: parameterised via meta.minLength so the
  tran... (continued)

1829 of 2944 branches covered (62.13%)

Branch coverage included in aggregate %.

259 of 319 new or added lines in 92 files covered. (81.19%)

3795 of 4892 relevant lines covered (77.58%)

716.91 hits per line