toga-ai 1.0.593 → 1.0.594

package/knowledge/2.0/apps/toga-blox/features/table.md

@@ -96,7 +96,10 @@ Per-column header controls, each a popover trigger with `data-active` / `data-op
   is hidden while the input is focused; both the trigger button and the icon span carry
   `data-active`. The clear button must not widen the input row (fixed-width menu).
 - **`HeaderFilterRange`** — numeric, modes exactly/moreThan/lessThan + a range toggle
-  (min/max); emits `{ key, value }[]` (`eq`/`min`/`max`/`between`).
+  (min/max); emits `{ key, value }[]` (`eq`/`min`/`max`/`between`). Reads its persisted
+  operator/values back from a `filterParams` prop (not `filterValue`, which collapses to the
+  literal `"active"` when a range filter is set); `PrimaryTableHeaderCell` must pass
+  `filterParams` through.
 - **`HeaderFilterMultiselect`** — checkbox list with "Select All"; emits comma-joined slugs.
 - **`HeaderFilterDate`** — calendar picker, modes exactly/before/after + range; converts
   `MM/DD/YYYY` ↔ URL `YYYY-MM-DD`; calendar + mode dropdown both portalled.
@@ -148,12 +151,31 @@ Per-column header controls, each a popover trigger with `data-active` / `data-op
   never for data fetching. A visible column can still *look* missing when `shrinkColumns` freezes
   it to a tiny width because its measured header+body content is minimal (see
   [primary-table-templates](primary-table-templates.md)).
+- **Filter presentational components must seed their internal mode/value state from props.**
+  The filter mode/operator survives the URL round-trip — it is persisted as a URL key suffix
+  (`_starts`/`_ends`/`_eq`/`_excludes` for text; `_min`/`_max`/`_eq`/`_between` for range),
+  rehydrated into TanStack `columnFilters` by toga25-supply `useServerTableUrlState`, and
+  carried through `PrimaryTableHeaderCell`. But `HeaderFilterSearch`/`HeaderFilterRange` are
+  remounted fresh each time a filter popover opens, so if they don't seed local state from
+  their props (`filterMode` / `filterParams`) they hard-default (`includes` for text,
+  `exactly` for range) and reopening a filter *shows the wrong mode* even though the applied
+  filter is correct. Fixed via a `useEffect` seeding `filterMode` from `filterModeProp` in
+  `HeaderFilterSearch`, and a rehydration effect keyed on `JSON.stringify(filterParams)` in
+  `HeaderFilterRange` that reconstructs mode + value(s) from the operator keys
+  (`eq`→Exactly, `min`→MoreThan, `max`→LessThan, `between`→range min/max).
 - **Table/surface meta is cached with `Infinity` staleTime/gcTime** (`useFetchTablePageMeta`), so
   after a DB metadata change (`TableViewFields`, `Core.RecordFields`) a **hard reload** is required
   to see it. And the app consumes toga-blox's built **`dist/`**, not `src/` — editing blox source
   requires `npm run build` before it takes effect at runtime.
 
 ## Change history
+- 2026-08-17 — Fixed: column filter **mode** was not restored when a filter popover was reopened
+  (text reverted to `includes`, range to `exactly`). Root cause: the URL round-trip and
+  `PrimaryTableHeaderCell` preserved the mode, but `HeaderFilterSearch` (destructured
+  `filterMode` as `filterModeProp` and never used it) and `HeaderFilterRange` (received no
+  operator info) never seeded internal state from props. Seeded both from props; added a
+  `filterParams` prop to `HeaderFilterRange` and passed it through `PrimaryTableHeaderCell`.
+  (apeterson)
 - 2026-08-17 — Added gotchas on meta→column mapping: field `type`/`precision` come from
   `Core.RecordFields` (not per-view) while `isCopyable`/`isVisible`/`isSortable`/`isFilterable` are
   per-view; `isVisible` is the only column gate; `accessorFn` dot-walks and needs the join;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.593",
+  "version": "1.0.594",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",