@praxisui/table 9.0.62 → 9.0.63

package/README.md

@@ -102,6 +102,8 @@ Use `resourcePath` when the host wants the table to enter backend schema/data mo
 
 `resourcePath` is enough only when the host already provides the Praxis API/CRUD wiring expected by the table runtime. In remote mode, the table derives columns from the backend schema contract and data from the backend resource/filter contract.
 
+Each standalone `praxis-filter` owns an isolated `GenericCrudService` instance. This is required when a composed page renders filters, tables, and related CRUD surfaces for different resources at the same time: one widget must never replace another widget's active schema/resource context.
+
 For schema-governed tables that need only a few editorial differences, keep
 `columns: []` and declare a schema projection. The runtime derives every visible
 column from `/schemas/filtered` and reapplies the overrides by canonical field
@@ -176,12 +178,35 @@ and emit schema/metadata diagnostics, but they do not emit `configChange` or a
 persistable `tableInputPatch`. Those authoring outputs are reserved for explicit
 user operations such as applying table settings or Quick Connect.
 
+Item actions discovered from HATEOAS are also runtime projections owned by the
+backend. When the overflow menu is opened before contextual discovery finishes,
+the menu shows its loading state and replaces that state with the governed
+actions in the same user interaction as soon as discovery settles. Hosts must
+not copy workflow actions into local table configuration or require users to
+close and reopen the menu to observe a capability that has already resolved.
+
 Row, selection and action events can include the read-only `resourceIdentity`
 materialized from the response schema. A valid explicit identity is preferred;
 otherwise a valid `idField` can produce a diagnostic key-only fallback. This
 context is for list/detail continuity and must not be copied into command
 controls or persistence payloads.
 
+When row selection is enabled with `mode: "row"` or `mode: "both"`, selectable
+rows use a single roving keyboard stop. `ArrowUp`, `ArrowDown`, `Home`, and `End`
+move focus without changing the selection; `Enter` and `Space` activate the
+focused row through the same `selectionChange` contract used by pointer input.
+Navigation is resolved against the table data model rather than the rows currently
+mounted in the DOM. In virtualized tables, `Home` and `End` therefore reach the
+first and last logical records and scroll the viewport before restoring focus.
+After refresh or filtering, focus follows the same stable row identity when that
+record still exists and otherwise falls back to the first available record. Set a
+stable `idField` for corporate datasets; index identity is only a last-resort local
+fallback and cannot preserve focus across reordering.
+The table receives its accessible name from `accessibility.ariaLabels.table`,
+then the table title, and finally the localized runtime fallback. Selection
+changes are announced in an isolated polite live region unless
+`accessibility.announcements.userActions` is explicitly `false`.
+
 ## Column resizing and auto-fit
 
 Column resizing is governed by `behavior.resizing`. When `enabled` is `true`,
@@ -403,10 +428,22 @@ Main authoring areas include:
 
 The package exports separate governed contracts for the two authoring documents: `PRAXIS_TABLE_AUTHORING_MANIFEST` owns `TableConfig`, including embedded filtering under `behavior.filtering`, while `PRAXIS_FILTER_AUTHORING_MANIFEST` owns the standalone `FilterConfig`. The standalone manifest never persists the controlled `value` DTO and does not expose Table query-builder operations or the nominal `submit` alias. `TABLE_AI_CAPABILITIES` / `TABLE_COMPONENT_AI_CAPABILITIES` remain the component capability discovery surface for the Table aggregate.
 
+Canonical table refinements preserve business meaning across preview, persistence, reopen and runtime rendering:
+
+- The global table title belongs to `toolbar.title` with the toolbar visible. It is distinct from a column header and must not be stored as an ad hoc root `title` or public widget input.
+- `column.format.set` materializes both the requested format and its compatible visual column type. For example, `BRL|symbol|2` produces a currency column while preserving the schema's numeric data shape and every unrelated column property.
+- `column.order.set` is a discrete visual move; order `0` means the first position. Its compiler emits a complete, collision-free order for all sibling columns so reopen and stable-sort runtimes cannot turn the edit into a visual no-op.
+- `column.sticky.set` only pins a column during horizontal scrolling. It never means move-to-start and never substitutes for `column.order.set`.
+
+Certification of these refinements must inspect the rendered table DOM—not only the authored JSON—including the toolbar title, visible header sequence, hidden-column absence and formatted cell content.
+
 ## Analytics And Rich Content
 
 The table can materialize analytic table projections produced by the canonical `x-ui.analytics` decision in `@praxisui/core`. Services such as `AnalyticsTableContractService` help hosts resolve analytic table contracts and data without reimplementing that projection.
 
+`AnalyticsTableStatsApiService.execute()` returns an `Observable<AnalyticsTableRow[]>`. The subscription owns the HTTP transport: unsubscribing aborts an in-flight stats request. `PraxisTable` applies the same `behavior.loading.requestTimeoutMs`, `behavior.loading.allowCancel`, retry, supersession and destruction lifecycle to REST resources and `analyticsProjection`, while preserving the last stable rows on cancellation or failure. Consumers that need a one-shot promise may use `firstValueFrom(...)` at their own orchestration boundary.
+When both `resourcePath` and `analyticsProjection` are present, the canonical `DataMode` precedence remains remote: the table cancels any analytical transport and does not mix rows from the stats endpoint with the resource collection.
+
 Detail rows can host governed rich content surfaces. Rich content semantics belong to the shared rich content/core contracts; the table provides the row-detail shell and host-mediated dispatch.
 When the actions column header combines an icon and a label, the table materializes that rich content with inline, non-wrapping layout. Column width may still be governed by the table contract, but the icon is not allowed to force the label onto a second line.
 When no bottom paginator or footer toolbar follows the data surface, the table closes its lower corners. When a bottom surface is present, the table keeps square lower corners so the stack remains visually continuous.