@iyulab/flex-table 0.36.0 → 0.38.0

package/CHANGELOG.md

@@ -1,5 +1,57 @@
 # Changelog
 
+## [0.38.0] - 2026-09-23
+
+### Fixed
+
+- 🔴 **Cell values follow the app's locale, not the browser's.** The built-in `number`, `date` and
+  `datetime` formatting called `toLocaleString()` without a locale, so values followed the runtime
+  default while the table's own menus and labels already followed `Locale`. An app set to Korean
+  and opened in an English browser showed Korean menus over `9/9/2026, 8:16:01 AM`. Values now go
+  through `@iyulab/components`' `formatDate`/`formatNumber`, which use `Locale.get()`, and the
+  numeric `format` patterns (`#,##0.00` and friends) use the same locale for their separators.
+- **A date-only value such as `"2026-09-09"` is read as that local date.** It was parsed as UTC
+  midnight, so in timezones behind UTC a `date` column showed the previous day.
+
+### Changed
+
+- 🔴 **The `@iyulab/components` peer range is now `>=1.27.0`** (was `>=1.24.0`). The formatters come
+  from that package's `format` module, which first shipped in 1.27.0; the old range admitted
+  versions without it.
+
+⚠ **Visible change:** if your app's `Locale` differs from the browser's language, dates and numbers in
+the table now appear in the app's format. Nothing changes when the two agree.
+
+## [0.37.0] - 2026-09-20
+
+### Fixed
+
+- **The column menu and the cell context menu stayed in English on a translated page.** 0.36.0 moved
+  the table's chrome text into a locale namespace, but the menus added in 0.35.0 were not part of
+  that move: their items, and the accessible name of the column-menu button, were written inline. On
+  a Korean page the same button therefore announced one language in its `title` and another in its
+  `aria-label`, and a screen-reader user heard English item names in the middle of a translated
+  grid — with no way to correct it, since the strings had no keys to register over. Every one of
+  those strings now goes through the namespace, including the cell context menu, the two menu
+  accessible names and the import drop target. Three keys name a column and carry a `{header}`
+  placeholder, so word order stays the translator's choice instead of being fixed by concatenation.
+  The built-in English wording is unchanged.
+
+### Documentation
+
+- **The README no longer lists every message key by hand.** That paragraph had gone stale once
+  already, and a hand-copied list is the only part of this documentation that can: the exported
+  `FlexTableMessageKey` cannot. It now names the groups and points at the type, which your editor
+  completes and the compiler checks.
+
+### Added
+
+- **The boolean filter's two options are translatable** (`booleanTrue` / `booleanFalse`). They read
+  `True` and `False` in every locale before this; the check and cross glyphs stay in the template,
+  since a symbol means the same thing in every language.
+- **`t()` and the exported namespace now interpolate.** `FlexTableMessageKey` gains the menu keys
+  above; registering a partial table still merges, so existing registrations keep working untouched.
+
 ## [0.36.0] - 2026-09-17
 
 ### Added

package/README.md

@@ -436,14 +436,25 @@ flexTableLocale.register('ja', {
 flexTableLocale.register('en', { replaceAll: 'Replace everything' });  // reword one string
 ```
 
-Keys cover the column header and menu (`showHiddenColumns`, `columnMenu`, `cellActions`,
-`noColumnsDefined`), cell comments (`addCommentPlaceholder`, `cancel`, `save`), the filter panel
-(`clear`, `blankCells`, `emptyOnly`, `nonEmptyOnly`, `blankAll`, `all`, `contains`, `startsWith`,
-`endsWith`, `wildcard`, `searchPlaceholder`, `valuePlaceholder`, `fromPlaceholder`,
-`toPlaceholder`) and find-and-replace (`findPlaceholder`, `findPrevious`, `findNext`, `matchCase`,
-`wholeCell`, `closeFind`, `replaceWithPlaceholder`, `replace`, `replaceAll`). `FlexTableMessageKey`
-is exported, so a missing or misspelled key is a type error rather than a string that silently falls
-back to its own name.
+The keys are grouped by where they appear: the column header and its menu, the items inside that
+menu, the cell context menu, cell comments, the filter panel, find-and-replace, and the import drop
+target. **`FlexTableMessageKey` is the list** — it is exported, so your editor completes it and a
+misspelled key is a type error rather than a string that silently falls back to its own name.
+
+> This paragraph used to enumerate every key by hand. It went stale once, and a hand-copied list is
+> the only thing here that can: the type cannot. If you want the full set, hover `FlexTableMessageKey`
+> or open `src/locale.ts`.
+
+Three of those keys name a column, and word order differs between languages, so they carry a
+`{header}` placeholder rather than being assembled by concatenation:
+
+```ts
+flexTableLocale.register('ja', {
+  columnMenuFor: '{header} の列メニュー',  // the column menu button's accessible name
+  columnMenuRegion: '{header} 列',                    // the open menu's accessible name
+  showColumn: '{header} を表示',                  // "show this hidden neighbour again"
+});
+```
 
 The filter operators `AND` and `OR` are not in the table, and neither are the glyphs that stand in
 for icons. They read the same in every language, and translating them makes them harder to