@praxisui/table 9.0.0-beta.33 → 9.0.0-beta.35
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -0
- package/ai/component-registry.json +139 -13
- package/fesm2022/{praxisui-table-praxisui-table-EYby6Zvn.mjs → praxisui-table-praxisui-table-DVrdSuiO.mjs} +613 -95
- package/fesm2022/{praxisui-table-table-ai.adapter-Bh0faxuI.mjs → praxisui-table-table-ai.adapter-utRTtk0G.mjs} +26 -1
- package/fesm2022/praxisui-table.mjs +1 -1
- package/package.json +10 -10
- package/src/lib/praxis-table.json-api.md +3 -2
- package/types/praxisui-table.d.ts +37 -6
package/README.md
CHANGED
|
@@ -87,6 +87,8 @@ Use `resourcePath` when the host wants the table to enter backend schema/data mo
|
|
|
87
87
|
|
|
88
88
|
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.
|
|
89
89
|
|
|
90
|
+
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.
|
|
91
|
+
|
|
90
92
|
## Runtime Inputs And Outputs
|
|
91
93
|
|
|
92
94
|
Common inputs:
|
|
@@ -124,6 +126,8 @@ The table owns table orchestration and rendering. It does not own backend resour
|
|
|
124
126
|
|
|
125
127
|
Fields generated from backend schema metadata can render compact corporate indicators when `field.presentation.presenter` is `chip`, `badge`, `status`, `iconValue`, or `microVisualization`. For chip/badge/status renderers, the table keeps `col.field` bound to the original field so sort, filter, export, and row actions continue to use the raw value. Omit `presentation.label` when the cell should display the row value; set it only when the schema intentionally wants a fixed visible label for every row.
|
|
126
128
|
|
|
129
|
+
For `iconValue`, `presentation.prefix` and `presentation.suffix` are rendered as separate rich text markers, not as part of the raw value. When an affix is present, the table suppresses the decorative icon by default so markers such as `#099` stay subtle and do not duplicate a tag/hash icon. Hosts can tune this through table CSS tokens such as `--p-table-icon-value-gap`, `--p-table-icon-value-affix-color`, `--p-table-icon-value-affix-opacity`, `--p-table-icon-value-affix-font-size`, `--p-table-icon-value-affix-font-weight`, `--p-table-icon-value-color`, and `--p-table-icon-value-font-weight`.
|
|
130
|
+
|
|
127
131
|
For schema-driven chip/badge/status cells, `presentation.tone` is mapped to table theme tokens: `neutral` becomes `basic`, `warning` becomes `warn`, and `info`, `success`, and `danger` are preserved. `presentation.appearance` maps to renderer variants `plain`, `soft`, `outlined`, and `filled`; `plain` renders without filled emphasis for dense enterprise tables.
|
|
128
132
|
|
|
129
133
|
Fields generated from backend schema metadata can render compact corporate micro visualizations when `field.presentation.presenter` is `microVisualization` and `field.presentation.visualization.surface` is `table-cell`. The canonical visualization shape is `PraxisPresentationVisualizationConfig` from `@praxisui/core`; the table only hosts the compact cell renderer.
|
|
@@ -136,6 +140,20 @@ For dense enterprise tables, `radial` table cells render the percent as adjacent
|
|
|
136
140
|
|
|
137
141
|
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.
|
|
138
142
|
|
|
143
|
+
## Toolbar Appearance
|
|
144
|
+
|
|
145
|
+
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.
|
|
146
|
+
|
|
147
|
+
```ts
|
|
148
|
+
const config: TableConfig = {
|
|
149
|
+
toolbar: {
|
|
150
|
+
visible: true,
|
|
151
|
+
position: 'top',
|
|
152
|
+
appearance: { preset: 'table-integrated' },
|
|
153
|
+
},
|
|
154
|
+
};
|
|
155
|
+
```
|
|
156
|
+
|
|
139
157
|
## Filtering And Row Actions
|
|
140
158
|
|
|
141
159
|
The package exports both the table runtime and `PraxisFilter` integration surfaces.
|