@praxisui/table 9.0.4-rc.9 → 9.0.4

package/README.md

@@ -99,6 +99,40 @@ 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.
 
+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
+name whenever the schema changes:
+
+```ts
+const config: TableConfig = {
+  columns: [],
+  columnProjection: {
+    source: 'schema',
+    include: ['competencia', 'salarioBruto', 'salarioLiquido'],
+    overrides: {
+      salarioLiquido: { sticky: 'end', width: '160px' },
+    },
+  },
+};
+```
+
+An unknown override never creates a client-only column, and the override cannot
+change the canonical `field`. Use explicit `columns` only when the page really
+owns a complete local projection rather than schema-derived defaults.
+
+The table editor keeps the expanded columns only in memory. On apply/save and
+in `configChange`, it serializes the contract back to `include` plus the actual
+`overrides`. Computed or other genuinely client-owned columns are preserved in
+`columnProjection.additions`; an addition cannot shadow a canonical schema
+field. This round-trip prevents customization from turning the compact page
+contract back into a schema copy.
+
+`include` is an ordered allowlist. Omit it only when every field marked as table
+visible by the backend belongs in the experience. Prefer it for financial,
+personal, or otherwise sensitive resources so future schema fields are not
+published implicitly.
+
 Optional collection operations such as export are not implied by a base route. Expose them only when backend capabilities or HATEOAS links prove that the operation is available.
 
 When the collection response exposes `_links.create` or a collection `capabilities` snapshot with create support, `PraxisTable` can materialize the canonical `create` toolbar action without requiring each host screen to duplicate labels, disabled state, schema URLs, or submit URLs. If the host provides `surface.open`, the action opens the create form as a governed collection surface; otherwise the table emits `toolbarAction` with the enriched action metadata for the composed host to handle.
@@ -218,23 +252,22 @@ The package exports both the table runtime and `PraxisFilter` integration surfac
 - Row actions can be declared in `config.actions.row.actions`.
 - Contextual row discovery can use backend HATEOAS/capabilities when enabled.
 - `visibleWhen` and `disabledWhen` use canonical JSON Logic.
+- Inline and overflow actions preserve their actionable origin. Overflow menus finish closing and restore the trigger before emitting the action, allowing dialogs and drawers with `restoreFocus` to return keyboard focus to the correct table control.
 
 The filter field manager follows the compact inline visual language and can be themed by hosts through
 `--pfx-field-manager-surface`, `--pfx-field-manager-on-surface`,
 `--pfx-field-manager-on-surface-muted`, `--pfx-field-manager-outline`,
-`--pfx-field-manager-focus-outline`, `--pfx-field-manager-search-surface`,
-`--pfx-field-manager-search-on-surface`, `--pfx-field-manager-search-placeholder`,
-`--pfx-field-manager-search-height`, `--pfx-field-manager-search-radius`,
-`--pfx-field-manager-search-font-size`, `--pfx-field-manager-search-line-height`,
-`--pfx-field-manager-search-font-weight`, `--pfx-field-manager-search-icon-size`,
+`--pfx-field-manager-focus-outline`, the shared `--praxis-collection-search-*` contract,
 `--pfx-field-manager-scrollbar-thumb`, `--pfx-field-manager-scrollbar-thumb-hover`,
 `--pfx-field-manager-scrollbar-track`, and `--pfx-field-manager-scrollbar-size`. Their defaults inherit
-the corresponding `--pdx-inline-*` tokens when available, then the semantic `--praxis-theme-*` roles,
-and finally Material system
-tokens; `--pfx-field-manager-search-radius` intentionally defaults to Material's full corner radius so
-the search focus ring and field share the same pill geometry. The runtime resolves every public
-`--pfx-field-manager-*` token from the host before applying its private fallback, so overrides take
-effect without CSS specificity workarounds. The scrollable field list reserves a stable scrollbar gutter
+the semantic `--praxis-theme-*` roles and finally Material system tokens. Collection searches in Table
+and Dynamic Fields share surface, foreground, placeholder, outline, focus, height, compact height,
+padding, gap, radius, icon/clear target, typography and motion variables. Set
+`--praxis-collection-search-radius: 0`, an intermediate radius such as `8px`, or `999px` on the global
+theme scope to select square, corporate-rounded or pill geometry without targeting internal selectors.
+The former Table-only `--pfx-field-manager-search-*` family is removed during beta so it cannot become
+a competing public contract. The runtime resolves every remaining public `--pfx-field-manager-*` token
+from the host before applying its private fallback. The scrollable field list reserves a stable scrollbar gutter
 and derives a contrasting thumb from the manager surface and on-surface roles, so its overflow affordance
 does not depend on application-global scrollbar styles. Native scrollbar auto-hide preferences can still
 control when the operating system displays the thumb. Because the manager renders in a CDK overlay, define host overrides on a global theme scope
@@ -299,6 +332,8 @@ The package also exports `PRAXIS_TABLE_AUTHORING_MANIFEST` for governed AI edits
 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.
 
 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.
 Governed embed nodes (`formRef`, `tableRef`, `chartRef`, `templateRef`, `diagramEmbed`) default to `renderMode: "reference"` when the field is omitted.
 `renderMode: "inline"` is an explicit intent for an owning runtime/provider to materialize the referenced surface inside the detail row; hosts must still keep the reference shell as the accessible fallback when the provider, data, or capability is unavailable.
 For charts, use `chartDocumentRef` or a governed `chartDocument` payload that follows the canonical `x-ui.chart` contract; do not place raw chart-engine options directly inside the table detail schema.