@epam/ai-dial-ui-kit 0.16.0-dev.45 → 0.16.0-dev.46

package/README.md

@@ -86,7 +86,7 @@ function App() {
 
 ### Optional: Markdown Components CSS
 
-If you're using markdown-related components (`DialMarkdownEditor` or `DialMarkdownEditorContainer`), you need to import the required CSS files globally in your application (e.g., in your root layout or main entry point):
+If you're using the `MarkdownEditor` (loaded through `LazyMarkdownEditor`), you need to import the required CSS files globally in your application (e.g., in your root layout or main entry point):
 
 ```tsx
 import '@uiw/react-markdown-preview/markdown.css';
@@ -309,8 +309,6 @@ breaking change and goes through the migration-guide process.
 | `dropdownSearch`    | `dial-kit-dropdown-search`        | The search row above the item list of a `searchable` `Dropdown`                                  |
 | `menuItem`          | `dial-kit-menuitem`               | One overlay row: a dropdown item, a `Select` option, a submenu trigger or child                   |
 | `menuItemCheck`     | `dial-kit-menuitem-check`         | The trailing check of a chosen `MenuItemMark.Check` row                                          |
-| `dropdownIcon`      | `dial-kit-dropdown-icon`          | The primary icon of a `DialDropdownIcon` trigger                                                 |
-| `dropdownIconCaret` | `dial-kit-dropdown-icon-caret`    | Its caret badge. Absent when `showCaret` is `false`                                              |
 | `tooltip`           | `dial-kit-tooltip`                | The bubble of a `Tooltip`                                                                        |
 | `interactiveTooltip` | `dial-kit-interactive-tooltip`   | The panel of an `InteractiveTooltip`                                                             |
 | `ellipsisTooltip`   | `dial-kit-ellipsis-tooltip`       | The text element of an `EllipsisTooltip`, which is also its trigger                              |
@@ -385,9 +383,8 @@ they render: `ThemeScope` (a `display: contents` wrapper), `MultiSelectTags`
 (`Tag`s), and `TooltipContainer` / `TooltipTrigger`.
 
 Two neighbouring elements are reached through props instead, and keep being: a
-`Dropdown`'s floating panel takes `listClassName`, a `Popup`'s backdrop takes
-`overlayClassName`, and the `DialDropdownIcon` trigger button takes
-`buttonClassName`.
+`Dropdown`'s floating panel takes `listClassName`, and a `Popup`'s backdrop
+takes `overlayClassName`.
 
 ## ♿ Accessibility
 
@@ -500,12 +497,12 @@ npm install @epam/ai-dial-ui-kit
 npm install react react-dom
 ```
 
-Add the editor packages only if you use the `@epam/ai-dial-ui-kit/editors`
-subpath. They are optional peers, so `npm install` stays quiet without them, and
-the kit only reaches for them when a `Lazy*` editor actually mounts:
+Add the editor package only if you use the Markdown editor
+(`LazyMarkdownEditor`). It is an optional peer, so `npm install` stays quiet
+without it, and the kit only reaches for it when the editor actually mounts:
 
 ``` bash
-npm install monaco-editor @monaco-editor/react @uiw/react-md-editor
+npm install @uiw/react-md-editor
 ```
 
 2. Import style in the root layout of the project:

package/dist/CHANGELOG.md

@@ -17,9 +17,12 @@ Versions match the git tags on the `development` branch.
 - **`styles.css` — Tailwind v4 preflight and browser baseline** — the stylesheet's preflight reaches every element on the host page, and v4's differs: `input`, `select` and `textarea` get a transparent background and no corner radius, `margin` and `padding` reset on every element, and the `hidden` attribute wins over a display utility. The v3 placeholder colour, the pointer cursor on buttons and the centred `<dialog>` are kept. The stylesheet now targets Safari 16.4+, Chrome 111+ and Firefox 128+. Tailwind v3's output already used native CSS nesting, so for most hosts this changes nothing.
   See [migration guide](migration-guides/0.16.0/tailwind-v4-stylesheet.md).
 
-- **`DialFileManager` — removed from the kit, use `@epam/ai-dial-react-file-manager`** — the legacy file manager, its `DialFoldersTree`, `DialDestinationFolderPopup`, `FileManagerProvider`, `useFileManagerContext`, `useDialFileManagerTabs`, the `DialFileManagerTabs` / `DialFileManagerActions` / `FileManagerColumnKey` enums, the `NAME_COLUMN` / `SIZE_COLUMN` / `UPDATED_AT_COLUMN` constants, its types, and the `./file-manager` subpath are gone. The file manager is developed in its own package, which exports every one of these names. Keeping a second, older copy in the kit meant two `DialFileManager`s that drifted apart. `DialFileName`, `DialFolderName`, `DialFileIcon`, `DialSharedEntityIndicator` and the file models stay.
+- **`DialFileManager` — removed from the kit, use `@epam/ai-dial-react-file-manager`** — the legacy file manager, its `DialFoldersTree`, `DialDestinationFolderPopup`, `FileManagerProvider`, `useFileManagerContext`, `useDialFileManagerTabs`, the `DialFileManagerTabs` / `DialFileManagerActions` / `FileManagerColumnKey` enums, the `NAME_COLUMN` / `SIZE_COLUMN` / `UPDATED_AT_COLUMN` constants, its types, and the `./file-manager` subpath are gone. The file manager is developed in its own package, which exports every one of these names. Keeping a second, older copy in the kit meant two `DialFileManager`s that drifted apart. The file models stay.
   See [migration guide](migration-guides/0.16.0/legacy-file-manager-removal.md).
 
+- **34 unused 1.0 components and `DialSchemaRenderer` — removed, use their 2.0 counterparts** — `DialAutocompleteInputValue`, `DialButtonDropdown`, `DialCheckbox`, `DialCollapsibleSidebar`, `DialConfirmationPopup`, `DialDraggableItem`, `DialDropdownIcon`, `DialFileIcon`, `DialFileName`, `DialFolderName`, `DialFormItem`, `DialFormPopup`, `DialGrid` (and its date renderer and helpers, also from `./grid`), `DialInputPopup`, `LazyDialJsonEditor`, `LazyDialMarkdownEditor` and `LazyDialMarkdownEditorContainer` (also from `./editors`), `DialNotification`, `DialNumberInput`, `DialPagination`, `DialPasswordInput`, `DialPopup`, `DialRadioButton`, `DialRadioGroup`, `DialRadioGroupPopupField`, `DialResizableContainer`, `DialSearch`, `DialSegmentedControl`, `DialSelect`, `DialSelectField`, `DialSharedEntityIndicator`, `DialSlider`, `DialSwitch`, `DialTagInput`, `DialTextarea` and `DialSchemaRenderer` are gone, with the types and enums only they used (`FormItemOrientation`, `SelectSize`, `SelectVariant`, `SegmentedControlOption`), the `DIAL_KIT_CLASS.dropdownIcon` / `dropdownIconCaret` entries and their `styles.css` rules. Neither DIAL Chat nor the DIAL Admin frontend uses them, and keeping them meant two components for one control. The schema types (`JsonSchema`, `SchemaRendererVariant` …) keep their names. `monaco-editor` and `@monaco-editor/react` are no longer optional peers: only the JSON editor used them.
+  See [migration guide](migration-guides/0.16.0/unused-legacy-components-removal.md).
+
 - **`CaptionText`, `ErrorText` (2.0) — no `role="alert"`** — every caption, including a plain field description, was an assertive live region, so a screen reader interrupted the user with helper text and every validation error, and a host that wrapped `ErrorText` in its own alert region announced the message twice. They are now plain text that a control points at: `Input`, `Textarea`, `Select` and the `SchemaRenderer` fields link their own `error` / `caption` through `aria-describedby` and set `aria-invalid` on an error, as `Slider`, `RadioGroup`, `RadioGroupPopupField` and `FileDropzone` already did. A host that renders `ErrorText` next to its own control links it the same way; a message that must interrupt, such as a failed submit, goes in a `role="alert"` region of the host's. Tests that found these messages with `getByRole('alert')` need another query. The legacy `DialCaptionText` / `DialErrorText` are unchanged. Reported from `ai-dial-chat`.
   See [migration guide](migration-guides/0.16.0/caption-text-no-alert-role.md).