@praxisui/table 9.0.0-beta.33 → 9.0.0-beta.34

package/README.md

@@ -87,6 +87,8 @@ Use `resourcePath` when the host wants the table to enter backend schema/data mo
 
 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.
+
 ## Runtime Inputs And Outputs
 
 Common inputs:
@@ -136,6 +138,20 @@ For dense enterprise tables, `radial` table cells render the percent as adjacent
 
 Use `config.ai.assistant.enabled = false` when a host needs to disable the embedded AI assistant entrypoint for a table instance. The default is enabled, so existing AI-enabled tables keep the current behavior without extra config. When the value changes to `false`, the component closes the assistant and removes the table assistant session from the shared assistant registry.
 
+## Toolbar Appearance
+
+Use `toolbar.appearance` for governed toolbar chrome instead of host CSS targeting internal classes. The built-in preset `table-integrated` composes toolbar and table as one operational block using public tokens for background, border, radius, shadow, spacing, and density.
+
+```ts
+const config: TableConfig = {
+  toolbar: {
+    visible: true,
+    position: 'top',
+    appearance: { preset: 'table-integrated' },
+  },
+};
+```
+
 ## Filtering And Row Actions
 
 The package exports both the table runtime and `PraxisFilter` integration surfaces.