@praxisui/table 10.0.0-rc.32 → 10.0.0-rc.34

package/README.md

@@ -438,7 +438,7 @@ For schema-driven chip/badge/status cells, `presentation.tone` is mapped to tabl
 
 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.
 
-For row-specific corporate indicators, declare `*Expr` properties inside the visualization, such as `valueExpr`, `valueSuffixExpr`, `totalExpr`, `targetExpr`, `baselineExpr`, `segmentsExpr`, `pointsExpr`, `thresholdsExpr`, `itemsExpr`, `toneExpr`, `ariaLabelExpr`, and `fallbackTextExpr`. `fallbackText` remains mandatory and static: it is the safe accessible fallback when the row does not provide the data required by the selected kind. In `PraxisTable`, string expressions accept row-context paths like `row.slaAtual` and controlled editor-style formulas such as `= row.slaAtual`; structured expressions use Json Logic. Use `valueSuffix`/`valueSuffixExpr` for compact `delta` units such as `%`, ` pp`, ` USD`, or ` dias`; the suffix is rendered literally, so include leading spacing when the unit requires it. Use `value`/`valueExpr` for `delta`, `bullet`, `radial`, and `harveyBall`; `points`/`pointsExpr` for `line`, `area`, `column`, and `comparison`; `segments`/`segmentsExpr` for `stackedBar`; and `items`/`itemsExpr` for `processFlow`.
+For row-specific corporate indicators, declare `*Expr` properties inside the visualization, such as `valueExpr`, `valueSuffixExpr`, `minExpr`, `maxExpr`, `totalExpr`, `targetExpr`, `baselineExpr`, `segmentsExpr`, `pointsExpr`, `thresholdsExpr`, `itemsExpr`, `toneExpr`, `ariaLabelExpr`, and `fallbackTextExpr`. `fallbackText` remains mandatory and static: it is the safe accessible fallback when the row does not provide the data required by the selected kind. In `PraxisTable`, string expressions accept row-context paths like `row.slaAtual`, numeric literals, and controlled editor-style formulas such as `= row.slaAtual`; structured expressions use Json Logic. Use `valueSuffix`/`valueSuffixExpr` for compact units such as `%`, ` pp`, ` ms`, ` USD`, or ` dias` across `delta`, `bullet`, `radial`, `harveyBall`, `line`, `area`, `column`, and `comparison`; the suffix is rendered literally, so include leading spacing when the unit requires it. Use `value`/`valueExpr` for `delta`, `bullet`, `radial`, and `harveyBall`; `points`/`pointsExpr` for `line`, `area`, `column`, and `comparison` (supporting numbers or `{ value, label }` points); `segments`/`segmentsExpr` for `stackedBar`; and `items`/`itemsExpr` for `processFlow`. For `line`, `area`, and `column`, `target`/`targetExpr` and `baseline`/`baselineExpr` project horizontal dashed reference lines inside the SVG plot, and `scaleScope: 'page'` synchronizes the `[min, max]` domain across all visible rows of the current page (while explicit row-level `min`/`minExpr` or `max`/`maxExpr` retain precedence over page bounds).
 
 Table-safe micro visualization kinds are `line`, `area`, `column`, `comparison`, `stackedBar`, `radial`, `harveyBall`, `bullet`, `delta`, and `processFlow`. For enterprise authoring, `delta`, `bullet`, `radial`, `harveyBall`, and `stackedBar` are recommended for rapid scanning in compact cells. `line`, `area`, and `column` are conditional on horizontal space; `comparison` is conditional because it increases row height; and `processFlow` is conditional because its steps must remain recognizable. Use an expanded row or related surface when those trade-offs do not directly support the decision. This is guidance rather than a runtime blocker, so existing governed documents remain faithfully rendered. If a row does not provide the minimum series/step data for a visual kind, the renderer keeps an accessible compact fallback with `role="img"` and the configured fallback or aria text.