hazo_ui 6.12.5 → 6.14.0

package/CHANGE_LOG.md

@@ -5,6 +5,96 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## v6.14.0 (2026-10-04)
+
+### Added — German (`de`) catalog and LocalePicker demo
+
+- New `src/locales/de.json`: German translation of all 219 keys in `en.json`
+  (flat dotted keys, identical key set, every `{{placeholder}}` preserved
+  verbatim). Consumers register it through hazo_i18n alongside `en`; the package
+  does not bundle non-English catalogs into `dist/`.
+- The German catalog was produced with the hazo_i18n pipeline, not by hand:
+  `translateMessages()` (export, then Gemini via `hazo_llm_api` per chunk, then
+  `importMessages()` with ICU/HTML/expansion validation). 9 chunks, 0 failed,
+  0 rejected. 14 non-blocking length-expansion warnings on very short strings
+  (e.g. `Save` to `Speichern`) were accepted; no translation was changed by hand.
+- Rationale: German is the first non-English catalog for hazo_ui, and it exercises
+  the hazo_i18n export/LLM/import round trip on a real package catalog.
+- Test-app: new `/locale-picker` page demoing `LocalePicker` (dropdown, compact and
+  inline variants; native, native+code and code display; flags) with real locale
+  alternates. Alternates point at a new `/set-locale` route that sets the
+  `NEXT_LOCALE` cookie and redirects back.
+- Test-app `i18n_runtime.ts` now registers the hazo_ui `en` and `de` catalogs under
+  the `hazo_ui` namespace, so hazo_ui components switch language in the test-app
+  through `HazoUiI18nProvider`. Previously they stayed English.
+
+### Fixed — dialog re-render loop on open
+
+- `HazoUiMultiFilterDialog` and `HazoUiMultiSortDialog` defaulted `initialFilters` /
+  `initialSortFields` to a fresh `[]` each render. Their open-time sync effect depends
+  on that prop, so every render reset state to a new array and looped until React
+  threw `RangeError: Invalid array length`. Defaults now reference a module-level
+  empty constant.
+- `filter_dialog_i18n.test.tsx`: the "explicit title wins" assertion queried
+  `getByText("Filter")`, which matched the still-mounted trigger button; it now asserts
+  no heading named "Filter".
+
+## v6.13.1 (2026-10-03)
+
+### Fixed — remaining hardcoded English strings now go through i18n
+
+- Wired the last user-facing strings that bypassed `useHazoUiT()`: RTE output
+  tabs (HTML / Plain Text / Raw HTML), RTE `(empty)` fallbacks, RTE link
+  placeholder, kanban filter `Clear`, kanban card edit aria-label, browser tab
+  close aria-label, notification unread-count aria-label, canvas text toolbar
+  font options (Sans / Serif / Mono), and markdown editor upload placeholder.
+- New en.json keys: `rte.tab_html`, `rte.tab_plain_text`, `rte.tab_raw_html`,
+  `rte.empty_content`, `rte.link_placeholder`, `kanban.clear`,
+  `browser_tab.close_aria`, `notification.unread_count`, `canvas_toolbar.font_sans`,
+  `canvas_toolbar.font_serif`, `canvas_toolbar.font_mono`,
+  `markdown.upload_placeholder`.
+- `hazo_browser_tab` and `notification_count_badge` now call `useHazoUiT()`.
+- Proper nouns (font family names), the `x` table-size separator and file-size
+  units are intentionally left untranslated.
+
+## v6.13.0 (2026-10-03)
+
+### Added — locale-aware i18n via `HazoUiI18nProvider`
+
+- `HazoUiI18nProvider` + `useHazoUiT()` (and types `HazoUiTFunction`,
+  `HazoUiI18nProviderProps`) are exported from the package root. The app mounts
+  the provider under `<HazoI18nProvider>` and passes a locale-aware `t`, e.g.
+  `useTranslations("hazo_ui")` from `hazo_i18n/client`. Same pattern as
+  hazo_auth's `HazoAuthProvider` `t` prop.
+- `defaultHazoUiT` exported for non-React callers (English, not locale-aware).
+- `permissionToast()` accepts an optional `t` option (defaults to English).
+
+### Fixed — hazo_ui rendered English in every locale
+
+- v6.12.x wired strings through `createPackageT`, which is locale-blind: every
+  component read the bundled English catalog regardless of the active locale.
+  Components now call `useHazoUiT()`, which returns the app-supplied locale
+  under a provider and the English catalog otherwise.
+- Missing keys in the active locale fall back to English per key (logged via
+  the hazo_ui logger) instead of throwing hazo_i18n's dev-mode error.
+
+### Changed
+
+- All 34 i18n-wired components use `useHazoUiT()` in the component body;
+  no module-level `t`. Prop defaults that used `t()` now resolve in the body
+  (`prop ?? t(key)`) — the public prop names are unchanged.
+- Helpers that need translation take `t` explicitly: `validateInput`
+  (flex_input), `auto_detect_fields` and `default_announcements` (kanban),
+  `renderErrorState` (table).
+- Without a provider, output is unchanged (English).
+
+### Test-app
+
+- `test-app/components/hazo_ui_i18n_root.tsx` bridges `useTranslations("hazo_ui")`
+  into the provider; mounted in the root layout.
+- `src/contexts/__tests__/hazo_ui_i18n.test.tsx` covers app-supplied locale,
+  per-key English fallback, and the no-provider default.
+
 ## v6.12.5 (2026-10-03)
 
 ### Changed — i18n string wiring (remaining hardcoded strings)

package/README.md

@@ -83,7 +83,24 @@ The `tw-animate-css` import replaces the legacy `tailwindcss-animate` plugin (us
 
 ## Internationalisation
 
-All built-in user-facing strings (dialogs, form inputs, rich text toolbar, sort dialog, kanban, loading/error states, kanban editor, markdown editor, image cropper, memory dropdown, celebration, date-range selector, etc.) resolve through `createPackageT("hazo_ui", en)` from `hazo_core/i18n`. The English catalogue lives in `src/locales/en.json` (207 keys). Prop defaults for labels resolve as `prop ?? t(key)`, so explicit props always override translations. Other locales are generated through `hazo_i18n` (see the test-app `/translations` page).
+All built-in user-facing strings resolve through a `t` function from `useHazoUiT()`. The English catalogue lives in `src/locales/en.json`, and `createPackageT("hazo_ui", en)` from `hazo_core/i18n` is the English fallback. Prop defaults for labels resolve as `prop ?? t(key)`, so explicit props always override translations.
+
+To render another locale, mount `HazoUiI18nProvider` under your hazo_i18n provider and pass a locale-aware `t` (same pattern as hazo_auth's provider):
+
+```tsx
+import { HazoI18nProvider, useTranslations } from "hazo_i18n/client";
+import { HazoUiI18nProvider } from "hazo_ui";
+
+function HazoUiI18nRoot({ children }: { children: React.ReactNode }) {
+  const t = useTranslations("hazo_ui");
+  return <HazoUiI18nProvider t={t}>{children}</HazoUiI18nProvider>;
+}
+
+// In your root layout, inside <HazoI18nProvider locale={locale} messages={messages}>:
+<HazoUiI18nRoot>{children}</HazoUiI18nRoot>
+```
+
+Without a provider, every component renders English. A key missing from the active locale falls back to English for that key. Other locales are generated through `hazo_i18n` (see the test-app `/translations` page).
 
 ## Color Configuration