@praxisui/table 9.0.0-beta.70 → 9.0.0-beta.72

package/README.md

@@ -183,6 +183,29 @@ The package exports both the table runtime and `PraxisFilter` integration surfac
 - Contextual row discovery can use backend HATEOAS/capabilities when enabled.
 - `visibleWhen` and `disabledWhen` use canonical JSON Logic.
 
+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`, and `--pfx-field-manager-search-icon-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. Because the manager renders in a CDK overlay, define host overrides on a global theme scope
+such as `html`, `body`, or the application theme class rather than only on the `praxis-filter` element.
+When using the `PraxisFilter` i18n input, `selectedFieldsSectionTitle` and
+`availableFieldsSectionTitle` customize the grouped field-manager headings; both are optional and
+default to the Portuguese runtime labels. Each manageable field preserves its authored
+`FieldMetadata.description` (falling back to its explicit tooltip/help metadata) as an information
+tooltip on hover and keyboard focus. This lets operators distinguish semantically different filters
+with similar labels—such as a single date, a date range, and a relative period—without the table
+runtime fabricating domain guidance.
+
 ```ts
 const config: TableConfig = {
   columns: [{ field: 'name', header: 'Name' }],
@@ -255,6 +278,7 @@ Main exports:
 
 - Separate local data mode from backend resource mode before deciding the minimum setup.
 - `enableCustomization` is opt-in and gates settings/authoring surfaces; it does not change the data mode.
+- `authoringCapability` optionally requires an exact capability from `EnterpriseRuntimeContext.capabilities` before those authoring surfaces are materialized. Use it for governed configuration; do not derive authorization from client-side usernames or roles.
 - Treat export as a governed optional operation, not as automatic support implied by `resourcePath`.
 - When `excel` is enabled in `export.formats`, the toolbar also exposes a current-page Excel export that downloads only the rows currently loaded in the table runtime with visible columns and formatted cell values. Full filtered exports continue to use the configured collection export provider.
 - Theme the table through Material/Praxis tokens instead of targeting internal descendants.