@epam/ai-dial-ui-kit 0.16.0-dev.68 → 0.16.0-dev.69

package/dist/CHANGELOG.md

@@ -29,8 +29,13 @@ Versions match the git tags on the `development` branch.
 - **`DialAnalyticsCard`, `DialAnalyticsBar`, `DialAnalyticsBarGroup`, `DialAnalyticsErrorTag`, `DialAnalyticsHistogram`, `DialSteps` — removed from the kit** — the legacy analytics set, its `AnalyticsCardVariant` enum, `DEFAULT_ANALYTICS_BAR_COLOR_MAP`, the `AnalyticsBarColorStop` / `AnalyticsCardCompareItem` types and the 1.0 `DialSteps` are gone. All of them already have 2.0 versions: `AnalyticsCard`, `AnalyticsBar`, `AnalyticsBarGroup` and `AnalyticsHistogram` (#978) and `Steps`; `DialAnalyticsErrorTag` is replaced by a red filled `Badge`. `Step` and `StepStatus` stay.
   See [migration guide](migration-guides/0.16.0/legacy-analytics-and-steps-removal.md).
 
+- **`Grid` (2.0) — empty state follows the Patterns 2.0 empty-state behaviour** — the grid drew a 100px `IconZoomCancel` instead of the shared `NoDataContent` card, said "No results found" / "Sorry, we couldn't find any results for your search." even when it simply had no rows, announced that message on every load, and left the column-filter case to ag-Grid's own unstyled no-matching-rows overlay. It now shows the shared card in both cases: no rows → `emptyStateTitle` (`'No items yet'`), `emptyStateDescription` (`'Items will appear here once they are added.'`) and the new `emptyStateAction`, announced only with the new `emptyStateLive`; filters leaving no rows → the new `filteredEmptyStateTitle` (`'No items found'`) / `filteredEmptyStateDescription` (`'Try a different search term or check your filters.'`), always announced. The grid sets `overlayComponentSelector` instead of `noRowsOverlayComponent`. Hosts that pass their own copy keep it; a host that filters `rowData` itself and relied on the announcement sets `emptyStateLive`.
+  See [migration guide](migration-guides/0.16.0/grid-empty-state-pattern.md).
+
 ### Added
 
+- **`Select` (2.0) — `filteredEmptyStateTitle` / `filteredEmptyStateDescription`, and the no-match message is announced** — a search that left no options showed the same `emptyStateTitle` as an empty list ("No options available"), so a host had to switch the copy on the query itself, and the message was never announced. The new props carry the "No [entities] found" copy for a non-empty query and fall back to `emptyStateTitle` / `emptyStateDescription`, so hosts that already switch the copy see no change; with a query the message is a `role="status"` region. Additive.
+
 - **`ErrorBoundary` (2.0)** — DIAL Chat (`react-error-boundary` with its own `ErrorAlert`) and Models Garden (a hand-written class around `StateScreen`) each built their crash screen, and only Models Garden announced the crash. It catches a render error in its subtree and shows a `StateScreen` with a warning badge and a focused `PrimaryButton`; the button calls `onReset` and renders the children again, or reloads the page when there is no `onReset`. `resetKeys` clears the error when a value such as the route path changes, and `onError` reports it. The crash is announced through an assertive `LiveRegion` mounted with the boundary, before the error. All text comes from props. No new public class: it is addressed through `dial-kit-state-screen` and `dial-kit-live-region`. Additive.
 
 - **`Spinner` (2.0) — `fullScreen`, `focusRef`** — Quick Apps, the editor and Models Garden each wrapped `Spinner` for their loading screen (`fullWidth` with `h-screen` or `h-dvh`, their own background and layer), and the three drifted apart. `fullScreen` makes the status root a fixed overlay on `bg-layer-base` at the kit's popup layer with the ring centred, so it covers the page and its header wherever it is rendered. `focusRef` makes the ring focusable (`tabIndex={-1}`) and points the ref at it, so a host can move focus to the loading state after a retry removes the focused control; the ring, not the overlay, takes focus, so the outline stays on screen. Both default off. Additive.