@luzmo/analytics-components-kit 1.0.3-beta.10 → 1.0.3-beta.11

package/README.md

@@ -1,12 +1,16 @@
 # Luzmo Analytics Components Kit
 
-**Internal Development Documentation** — A collection of analytics-focused web components built with [Lit](https://lit.dev/) for building Luzmo dashboard interfaces.
+A collection of web components for building analytics interfaces with Luzmo. Built with [Lit](https://lit.dev/) and designed to work seamlessly with Luzmo's visualization platform.
 
-## Table of contents
+ACK produces and edits chart configuration (type, slots, options, filters). It does not render charts itself. You hand the configuration to Luzmo Embed (`@luzmo/embed`), which renders the visualization.
 
-- [Installation](#installation)
-- [Browser Support](#browser-support)
-- [License](#license)
+> **Full documentation**: for detailed guides, component APIs, theming, and examples, see the [Analytics Components Kit docs](https://developer.luzmo.com/guide/ack--overview).
+
+## How it works
+
+1. **Configure**: users interact with ACK components to pick data fields, assign them to chart slots, set options, and define filters. Each change fires an event your app captures.
+2. **Store**: your app keeps the resulting `slotsContents`, `options`, and `filters` as its own state. ACK follows a one-way data flow: your app is the single source of truth.
+3. **Render**: pass `{ type, slots, options, filters }` into a Luzmo Embed component (`luzmo-embed-viz-item` for a single chart, or let `luzmo-item-grid` render a multi-chart layout).
 
 ## Installation
 
@@ -14,16 +18,321 @@
 npm install @luzmo/analytics-components-kit
 ```
 
-For full documentation — components, patterns, and API reference, please visit https://developer.luzmo.com/guide/ack--overview .
+To render the configured charts, also install Luzmo Embed (optional):
+
+```bash
+npm install @luzmo/embed
+```
+
+Optional framework wrappers for embedding: `@luzmo/react-embed`, `@luzmo/ngx-embed`, `@luzmo/vue-embed`.
+
+> **Important**: This package is linked to `@luzmo/dashboard-contents-types@1.0.31`. Ensure you are using this version when working with `slotsContents`, `slotConfiguration`, `options`, and grid configurations.
+
+## Authentication
+
+Every component that fetches data needs an **embed authorization** token. This is a short-lived, scoped token, not your org API credentials. It follows a two-tier model:
+
+1. **Server-side**: your backend uses your org API key/token (environment variables, never shipped to the client) to call the Luzmo SDK and generate an embed authorization object.
+2. **Client-side**: your frontend fetches that object from your backend and reads the `authKey` / `authToken` fields (or `id` / `token` if you return the raw Luzmo authorization object). These are passed to every component.
+
+Set `auth-key` and `auth-token` consistently on every component that accesses data:
+
+```html
+<luzmo-data-field-panel
+  auth-key="your-auth-key"
+  auth-token="your-auth-token"
+></luzmo-data-field-panel>
+
+<luzmo-item-slot-drop-panel
+  auth-key="your-auth-key"
+  auth-token="your-auth-token"
+  item-type="bar-chart"
+>
+</luzmo-item-slot-drop-panel>
+```
+
+For the full walkthrough (generating embed tokens, token management, and multi-tenancy), see the [authentication patterns guide](https://developer.luzmo.com/guide/ack--patterns).
+
+## Available Components
+
+Import individual components so bundlers can tree-shake unused code. eg.
+
+```typescript
+import '@luzmo/analytics-components-kit/data-field-panel';
+import '@luzmo/analytics-components-kit/item-slot-drop-panel';
+import '@luzmo/analytics-components-kit/item-option-panel';
+```
+
+### Data Fields
+
+Present the columns and formulas from a dataset so users can pick the data they want to visualize.
+
+| Component        | Import                                             | Description                                                                          | Reference                                                                                      |
+| ---------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
+| Data Field       | `@luzmo/analytics-components-kit/data-field`       | Single draggable representation of a dataset column or formula                       | [Docs](https://developer.luzmo.com/guide/ack--components--data-fields--luzmo-data-field)       |
+| Data Field Panel | `@luzmo/analytics-components-kit/data-field-panel` | Panel listing all fields for one or more datasets, with search and dataset switching | [Docs](https://developer.luzmo.com/guide/ack--components--data-fields--luzmo-data-field-panel) |
+
+### Data Slots
+
+Let users assign data fields to chart slots (e.g. `x-axis`, `measure`, `legend`). Drag-and-drop for desktop, dropdown pickers for compact/mobile layouts.
+
+| Component              | Import                                                   | Description                                                              | Reference                                                                                           |
+| ---------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- |
+| Item Slot Drop         | `@luzmo/analytics-components-kit/item-slot-drop`         | Drop target for a single slot                                            | [Docs](https://developer.luzmo.com/guide/ack--components--data-slots--luzmo-item-slot-drop)         |
+| Item Slot Drop Panel   | `@luzmo/analytics-components-kit/item-slot-drop-panel`   | All slot drop targets for a chart type (drag & drop); auto constraints   | [Docs](https://developer.luzmo.com/guide/ack--components--data-slots--luzmo-item-slot-drop-panel)   |
+| Item Slot Picker       | `@luzmo/analytics-components-kit/item-slot-picker`       | Dropdown picker for a single slot                                        | [Docs](https://developer.luzmo.com/guide/ack--components--data-slots--luzmo-item-slot-picker)       |
+| Item Slot Picker Panel | `@luzmo/analytics-components-kit/item-slot-picker-panel` | Dropdown pickers for all slots (no drag & drop); optional dataset picker | [Docs](https://developer.luzmo.com/guide/ack--components--data-slots--luzmo-item-slot-picker-panel) |
+
+> Prefer the panel components (`data-field-panel`, `item-slot-drop-panel`, `item-slot-picker-panel`) over the individual primitives: panels auto-load slot configs and apply inter-slot constraints for you (e.g. "no multiple measures when the legend is filled"). Use the primitives only when you need custom layout/styling and can handle constraints yourself.
+
+### Item Options
+
+Let users adjust how a chart looks and behaves (colors, labels, chart mode, legend position, ...).
+
+| Component         | Import                                              | Description                                       | Reference                                                                                        |
+| ----------------- | --------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
+| Item Option       | `@luzmo/analytics-components-kit/item-option`       | Single option control (expose only what you need) | [Docs](https://developer.luzmo.com/guide/ack--components--item-options--luzmo-item-option)       |
+| Item Option Panel | `@luzmo/analytics-components-kit/item-option-panel` | Full grouped options editor for a chart type      | [Docs](https://developer.luzmo.com/guide/ack--components--item-options--luzmo-item-option-panel) |
+
+Individual option control editors are also exported for fully custom option UIs: `item-option-action-button-group`, `item-option-color-palette-picker`, `item-option-color-picker`, `item-option-color-range`, `item-option-multi-language-field`, `item-option-number-field`, `item-option-picker`, `item-option-position-picker`, `item-option-positions-number-field`, `item-option-radio-button-group`, `item-option-slider`, `item-option-switch`, and `item-option-text-field`.
+
+### Filters
+
+| Component | Import                                    | Description                             | Reference                                                                         |
+| --------- | ----------------------------------------- | --------------------------------------- | --------------------------------------------------------------------------------- |
+| Filters   | `@luzmo/analytics-components-kit/filters` | Filter editor with nested AND/OR groups | [Docs](https://developer.luzmo.com/guide/ack--components--filters--luzmo-filters) |
+
+`<luzmo-filters>` outputs the standard Luzmo filter format (`ItemFilterGroup[]` from `@luzmo/dashboard-contents-types`), compatible with `luzmo-embed-viz-item`'s `filters` property and `luzmo-item-grid` items' `filters`.
+
+### Chart rendering
+
+| Component | Import                                      | Description                                                                          | Reference                                                                                   |
+| --------- | ------------------------------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
+| Item Grid | `@luzmo/analytics-components-kit/item-grid` | Interactive grid to arrange, resize, and manage multiple charts (renders internally) | [Docs](https://developer.luzmo.com/guide/ack--components--chart-rendering--luzmo-item-grid) |
+
+To render a single chart, use `luzmo-embed-viz-item` from `@luzmo/embed` (not part of this kit); see [Rendering](#rendering).
+
+## Usage: Drag & Drop Data Flow
+
+1. Add `<luzmo-data-field-panel>` for data fields and `<luzmo-item-slot-drop-panel>` for slots (or `<luzmo-item-slot-picker-panel>` for mobile).
+2. Feed the panel its data via `dataset-ids` (auto-fetch, with `api-url` + auth) or `datasetsDataFields` (your own data).
+3. Set `item-type` (e.g. `bar-chart`) on the slot panel and listen to `luzmo-slots-contents-changed` to capture the slots state.
+4. Treat `slotsContents` as your app state (re-apply it after each change for one-way data flow) and use `{ type, slots, options, filters }` to render the configured chart.
+
+```typescript
+import '@luzmo/analytics-components-kit/data-field-panel';
+import '@luzmo/analytics-components-kit/item-slot-drop-panel';
+
+const fieldsPanel = document.querySelector('luzmo-data-field-panel')!;
+const dropPanel = document.querySelector('luzmo-item-slot-drop-panel')!;
+
+for (const panel of [fieldsPanel, dropPanel]) {
+  panel.apiUrl = 'https://api.luzmo.com'; // EU (default); US: https://api.us.luzmo.com; or your VPC host
+  panel.authKey = 'your-auth-key';
+  panel.authToken = 'your-auth-token';
+}
+
+fieldsPanel.datasetIds = ['your-dataset-id'];
+
+// Tell the slot panel which chart type to build slots for (bar-chart, line-chart, ...)
+dropPanel.itemType = 'bar-chart';
+
+dropPanel.addEventListener('luzmo-slots-contents-changed', (event) => {
+  const { slotsContents } = (event as CustomEvent<{ slotsContents: unknown[] }>).detail;
+  dropPanel.slotsContents = slotsContents; // re-apply state (one-way data flow)
+
+  // `slotsContents` is the `slots` half of the chart state; combine it with the
+  // chart `type`, `options`, and `filters` you track to render (see Rendering).
+});
+```
+
+`item-slot-drop-panel` and `item-slot-picker-panel` emit the same `luzmo-slots-contents-changed` event, so you can share one handler and swap them with CSS media queries for responsive layouts.
+
+See the [Data Field Panel reference](https://developer.luzmo.com/guide/ack--components--data-fields--luzmo-data-field-panel) for the full list of properties, events, and examples.
+
+## Rendering
+
+ACK produces the configuration; `luzmo-embed-viz-item` (from `@luzmo/embed`) renders it. Store the state your ACK components emit and map it onto the viz item:
+
+| Viz item input | Controlled by       | ACK component(s)                                                                       |
+| -------------- | ------------------- | -------------------------------------------------------------------------------------- |
+| `type`         | which chart to draw | slot/option components via `item-type`                                                 |
+| `slots`        | data the chart uses | `item-slot-drop`, `item-slot-drop-panel`, `item-slot-picker`, `item-slot-picker-panel` |
+| `options`      | look and behavior   | `item-option`, `item-option-panel`                                                     |
+| `filters`      | rows included       | `filters`                                                                              |
+
+```typescript
+import '@luzmo/embed';
+
+const vizItem = document.querySelector('luzmo-embed-viz-item')!;
+vizItem.appServer = 'https://app.luzmo.com'; // EU (default); US: https://app.us.luzmo.com; or your VPC host
+vizItem.apiHost = 'https://api.luzmo.com'; // EU (default); US: https://api.us.luzmo.com; or your VPC host
+vizItem.authKey = 'your-auth-key';
+vizItem.authToken = 'your-auth-token';
+
+// Map your ACK-produced state onto the viz item (your app is the single source of truth)
+vizItem.type = itemType; // chart type
+vizItem.slots = slotsContents; // from luzmo-slots-contents-changed
+vizItem.options = options; // from luzmo-options-changed
+vizItem.filters = filters; // from luzmo-filters-changed
+```
+
+See the Flex reference and the "Using luzmo-embed-viz-item with the kit" guide in the [ACK docs](https://developer.luzmo.com/guide/ack--overview) for every viz item property, event, and method.
+
+## Item Grid
+
+Use `<luzmo-item-grid>` to render and edit a dashboard grid of charts (it embeds charts internally). Each item needs an `id`. Choose one of two modes:
+
+- **Uncontrolled**: seed the grid once with the `initial-items` attribute; the grid manages layout state internally.
+- **Controlled**: drive the grid with the `items` property and keep your app state in sync from the events.
+
+```ts
+const grid = document.querySelector('luzmo-item-grid')!;
+grid.appServer = 'https://app.luzmo.com'; // EU (default); US: https://app.us.luzmo.com; or your VPC host
+grid.apiHost = 'https://api.luzmo.com'; // EU (default); US: https://api.us.luzmo.com; or your VPC host
+grid.authKey = 'your-auth-key';
+grid.authToken = 'your-auth-token';
+
+grid.items = [
+  {
+    id: 'chart-1',
+    type: 'bar-chart',
+    position: { col: 0, row: 0, sizeX: 24, sizeY: 20 },
+    options: { mode: 'grouped' },
+    slots: [
+      // Each slot references a chart-type slot by `name` (bar-chart: y-axis, measure, legend).
+      // Slot content describes the column/formula, not just its ids.
+      {
+        name: 'y-axis',
+        content: [
+          {
+            datasetId: 'b35d4aaf-5f36-47a0-94e6-91a989d1635f',
+            columnId: 'cb43b7f7-ede1-410f-88c1-5a93e1f9b92c',
+            label: { en: 'Campaign' },
+            type: 'hierarchy'
+          }
+        ]
+      },
+      {
+        name: 'measure',
+        content: [
+          {
+            datasetId: 'b35d4aaf-5f36-47a0-94e6-91a989d1635f',
+            columnId: '8953c794-830c-46e5-bdb7-eee9b15dd8f5',
+            label: { en: 'Opened emails' },
+            type: 'hierarchy',
+            aggregationFunc: 'count',
+            format: ',.0f'
+          }
+        ]
+      }
+    ]
+  }
+];
+
+// Controlled mode: re-apply the corrected items after each layout change
+grid.addEventListener('luzmo-item-grid-layout-changed', (e) => {
+  grid.items = (e as CustomEvent).detail.updatedItems;
+});
+```
+
+> Slot content is a full field descriptor (`datasetId`/`columnId` or `formulaId`, plus `label`, `type`, and modifiers like `aggregationFunc`, `level`, or `format`), not just an id pair. The easiest way to produce valid slot content is to let the drag & drop panels emit it; see [Usage: Drag & Drop Data Flow](#usage-drag--drop-data-flow).
+
+Key events: `luzmo-item-grid-ready`, `luzmo-item-grid-layout-changed`, `luzmo-item-grid-item-action` (cancelable), and `luzmo-item-grid-item-states-changed`. Imperative helpers (`addGridItem`, `removeGridItem`, `cloneGridItem`, `updateGridItem*`) return the updated `GridItemData[]`.
+
+See the [Item Grid reference](https://developer.luzmo.com/guide/ack--components--chart-rendering--luzmo-item-grid) for controlled vs uncontrolled details, all properties, events, methods, and examples.
+
+## Utilities
+
+Import helpers from `@luzmo/analytics-components-kit/utils` when you need ACK-compatible data or chart-state transformations without mounting a component.
+
+```typescript
+import { loadDataFieldsForDatasets, switchItem } from '@luzmo/analytics-components-kit/utils';
+import { itemTypes } from '@luzmo/analytics-components-kit/item-list';
+
+// Load datasets with their columns/formulas, converted to component-ready data fields
+const datasets = await loadDataFieldsForDatasets(['dataset-id-1'], {
+  // apiUrl: EU (default) https://api.luzmo.com; US: https://api.us.luzmo.com; or your VPC host
+  dataBrokerConfig: { apiUrl: 'https://api.luzmo.com', authKey: 'your-auth-key', authToken: 'your-auth-token' }
+});
+
+// Switch chart type while preserving compatible slot data
+const newItem = await switchItem({ oldItemType: 'bar-chart', newItemType: 'line-chart', slots, options });
+
+// Build a chart picker from the available chart types
+const chartOptions = itemTypes.map((item) => ({ label: item.label, value: item.type }));
+```
+
+See the [Utilities reference](https://developer.luzmo.com/guide/ack--utilities) for signatures, return types, behavior notes, and more examples.
+
+## Types
+
+Import TypeScript types from the dedicated entrypoint:
+
+```typescript
+import type {
+  DatasetDataField,
+  SlotContentsChangedEventDetail,
+  SlotConstraintTriggeredEventDetail,
+  ItemFilterGroup
+} from '@luzmo/analytics-components-kit/types';
+```
+
+Runtime values are exported from the main package (or `@luzmo/analytics-components-kit/utils`), e.g. `import { PeriodOverPeriodCondition } from '@luzmo/analytics-components-kit';`.
+
+## Language & Localization
+
+Components render labels, placeholders, and data in the language you specify via two properties:
+
+- `language`: UI language (button labels, slot names, menu items). Supported: `en`, `nl`, `fr`, `de`, `es`.
+- `content-language`: locale-aware formatting and data labels (number formats, date patterns, column names). Defaults to `language`.
+
+```html
+<luzmo-data-field-panel
+  language="nl"
+  content-language="nl"
+></luzmo-data-field-panel>
+```
+
+See the [patterns guide](https://developer.luzmo.com/guide/ack--patterns) for multi-language data labels.
+
+## Item Definitions
+
+Each chart type has a slots config, options config, and context config. Access them through dedicated subpaths (one named export per item type):
+
+```typescript
+import { itemGroups, itemTypes, itemList } from '@luzmo/analytics-components-kit/item-list';
+import { barChartSlotsConfig } from '@luzmo/analytics-components-kit/item-slots-configs';
+import { barChartOptionsConfig } from '@luzmo/analytics-components-kit/item-options-configs';
+import { barChartContextConfig } from '@luzmo/analytics-components-kit/item-context-configs';
+```
+
+Use `itemTypes` for the complete, authoritative list of chart types (`bar-chart`, `line-chart`, `donut-chart`, `scatter-plot`, `heat-map`, tables, numbers, and more). See the [Item Definitions guide](https://developer.luzmo.com/guide/ack--item-definitions) for details.
 
-For a concrete step-by-step guide on how to build a custom dashboard editor with these components, please visit https://developer.luzmo.com/guide/guides--building-a-dashboard-studio .
+## Theming
+
+Components are themed via global CSS custom properties (`--luzmo-*`). Set them on `:root` / `html` for app-wide theming, or scope them to a container. eg.
+
+```css
+:root {
+  --luzmo-primary: #4434ff;
+  --luzmo-background-color: #ffffff;
+  --luzmo-font-color: #333;
+}
+```
+
+Each component also exposes `--luzmo-{component}-*` variables for fine-grained overrides (only override variables prefixed with `--luzmo-`):
+
+```css
+luzmo-item-slot-drop {
+  --luzmo-item-slot-drop-height: 3rem;
+  --luzmo-item-slot-drop-border-radius: 8px;
+}
+```
 
 ## Browser Support
 
-- Last 2 versions of Chrome
-- Last 2 versions of Firefox
-- Last 2 versions of Safari
-- Last 2 versions of Edge
+Last 2 versions of Chrome, Firefox, Safari, and Edge.
 
 ## License
 

package/components/ai-chat/ai-chat.d.ts

@@ -19,10 +19,10 @@ import type { AiPromptAgent, AiPromptItemTask, AiPromptScreenMode, DashboardStat
  * See {@link AiChatSession} / createAiChatSession for callbacks and external fetchStreaming.
  * @fires {CustomEvent<AiChatStepEvent>} luzmo-step - Fired for every incremental, kit-assembled event during a streamed response (decision, text, progress, dashboard-title/layout/item, chart, interrupt, plus forward-by-default unrecognized chunks). Use `isRecognizedStep` to narrow.
  * @fires {CustomEvent<AiChatCompleteEvent>} luzmo-complete - Fired exactly once per response with the authoritative final result (dashboard/chart/name) or an `error`.
- * @fires luzmo-message-sent - Fired when a user sends a message
- * @fires luzmo-datasets-changed - Fired when the selected datasets change
- * @fires luzmo-conversation-id-changed - Fired when the conversation ID is updated from the API
- * @fires luzmo-stop - Fired when an in-flight prompt is stopped
+ * @fires {CustomEvent<AiChatMessageSentEventDetail>} luzmo-message-sent - Fired when a user sends a message
+ * @fires {CustomEvent<AiChatDatasetsChangedEventDetail>} luzmo-datasets-changed - Fired when the selected datasets change
+ * @fires {CustomEvent<AiChatConversationIdChangedEventDetail>} luzmo-conversation-id-changed - Fired when the conversation ID is updated from the API
+ * @fires {CustomEvent<void>} luzmo-stop - Fired when an in-flight prompt is stopped
  *
  * @property {string} --luzmo-ai-chat-background - Background of the chat container
  * @property {string} --luzmo-ai-chat-border-radius - Border radius of the chat container
@@ -69,6 +69,10 @@ export declare class LuzmoAiChat extends LuzmoElement {
      * When true, disables the entire chat interface
      */
     disabled: boolean;
+    /**
+     * When true, shows a stop control on the prompt input while a response is generating
+     */
+    stoppable: boolean;
     /**
      * When true, shows context menu (3 dots) on assistant messages
      */

package/components/ai-chat/empty-state/ai-chat-empty-state.d.ts

@@ -5,7 +5,7 @@ import type { AiChatEmptyStateSuggestion } from './types';
 /**
  * @customElement luzmo-ai-chat-empty-state
  * @summary Empty state for AI chat with title, subtitle, and prompt suggestions.
- * @fires luzmo-suggestion-selected - Fired when the user selects a suggestion chip. `event.detail`: `{ label, prompt, selectedDatasets? }`.
+ * @fires {CustomEvent<AiChatEmptyStateSuggestionSelectedDetail>} luzmo-suggestion-selected - Fired when the user selects a suggestion chip
  *
  * @property {string} --luzmo-ai-chat-empty-state-header-actions-gap - Gap between the title and the actions block
  * @property {string} --luzmo-ai-chat-empty-state-actions-gap - Gap between the actions label and suggestion chips

package/components/ai-chat/index.cjs

@@ -17,4 +17,4 @@
  * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  * SOFTWARE.
  * */
-Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("../ai-chat-Du1gOCyo.cjs");exports.AiChatSession=e.i,exports.AiChatSessionController=e.r,exports.LuzmoAiChat=e.n,exports.LuzmoAiChatEmptyState=e.T,exports.buildAiPromptDeleteRequest=e._,exports.buildAiPromptProperties=e.v,exports.buildAiPromptRequest=e.y,exports.buildAnalystAiPromptProperties=e.b,exports.buildDashboardAiPromptProperties=e.x,exports.buildItemAiPromptProperties=e.S,exports.chartToItemAsset=e.C,exports.createAiChatSession=e.a,exports.createInitialProgress=e.f,exports.createInitialStreamState=e.o,exports.createStreamHandler=e.s,exports.extractChartFromChunk=e.u,exports.extractDashboardFromChunk=e.d,exports.fetchStreamingResponse=e.m,exports.getAgentStreamDefinition=e.c,exports.getAiPromptUrl=e.w,exports.hasProgressChunk=e.p,exports.isRecognizedStep=e.t,exports.parseStreamLine=e.h,exports.processStreamChunk=e.l,exports.readNdjsonStream=e.g;
+Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("../ai-chat-8O_eA0_D.cjs");exports.AiChatSession=e.i,exports.AiChatSessionController=e.r,exports.LuzmoAiChat=e.n,exports.LuzmoAiChatEmptyState=e.T,exports.buildAiPromptDeleteRequest=e._,exports.buildAiPromptProperties=e.v,exports.buildAiPromptRequest=e.y,exports.buildAnalystAiPromptProperties=e.b,exports.buildDashboardAiPromptProperties=e.x,exports.buildItemAiPromptProperties=e.S,exports.chartToItemAsset=e.C,exports.createAiChatSession=e.a,exports.createInitialProgress=e.f,exports.createInitialStreamState=e.o,exports.createStreamHandler=e.s,exports.extractChartFromChunk=e.u,exports.extractDashboardFromChunk=e.d,exports.fetchStreamingResponse=e.m,exports.getAgentStreamDefinition=e.c,exports.getAiPromptUrl=e.w,exports.hasProgressChunk=e.p,exports.isRecognizedStep=e.t,exports.parseStreamLine=e.h,exports.processStreamChunk=e.l,exports.readNdjsonStream=e.g;

package/components/ai-chat/index.d.ts

@@ -4,7 +4,7 @@ declare global {
         'luzmo-ai-chat': LuzmoAiChat;
     }
 }
-export type { ProgressTreeNode } from '../../types/ai-chat.types';
+export type { ProgressTreeNode, AiChatMessageSentEventDetail, AiChatDatasetsChangedEventDetail, AiChatConversationIdChangedEventDetail } from '../../types/ai-chat.types';
 export { isRecognizedStep } from './ai-chat-events';
 export type { AiChatCompleteEvent, AiChatRecognizedStepType, AiChatStepBase, AiChatStepEvent, RecognizedStepEvent, UnknownStepEvent } from './ai-chat-events';
 export { AiChatSession, AiChatSessionController, createAiChatSession } from './session';

package/components/ai-chat/index.js

@@ -24,5 +24,5 @@
 		e.setAttribute("data-luzmo-vars", ""), e.textContent = "html{--luzmo-animation-duration: 0.15s;--luzmo-border-color: rgba(var(--luzmo-border-color-rgb), 0.1);--luzmo-border-color-hover: rgba(var(--luzmo-border-color-rgb), 0.15);--luzmo-border-color-down: rgba(var(--luzmo-border-color-rgb), 0.3);--luzmo-border-color-focus: rgba(var(--luzmo-border-color-rgb), 0.15);--luzmo-border-color-rgb: 0, 0, 0;--luzmo-border-color-full: rgb(180, 180, 180);--luzmo-border-color-full-hover: color-mix(in oklch, var(--luzmo-border-color-full), black 25%);--luzmo-border-color-full-down: color-mix(in oklch, var(--luzmo-border-color-full), black 45%);--luzmo-border-color-full-focus: color-mix(in oklch, var(--luzmo-border-color-full), black 25%);--luzmo-border-color-disabled: #dddddd;--luzmo-border-radius: 6px;--luzmo-border-radius-s: 4px;--luzmo-border-radius-l: 8px;--luzmo-border-radius-xl: 12px;--luzmo-border-radius-full: 999rem;--luzmo-background-color: #ffffff;--luzmo-background-color-rgb: 255, 255, 255;--luzmo-background-color-disabled: #eeeeee;--luzmo-background-color-hover: color-mix( in oklch, color-mix(in oklch, var(--luzmo-background-color), var(--luzmo-primary) 5%), black 1.5% );--luzmo-background-color-down: color-mix(in oklch, color-mix(in oklch, var(--luzmo-background-color), var(--luzmo-primary) 7%), black 1%);--luzmo-background-color-focus: color-mix( in oklch, color-mix(in oklch, var(--luzmo-background-color), var(--luzmo-primary) 5%), black 1.5% );--luzmo-background-color-highlight: rgb(240, 240, 240);--luzmo-background-color-highlight-disabled: rgb(245, 245, 245);--luzmo-background-color-highlight-hover: color-mix(in oklch, var(--luzmo-background-color-highlight), black 25%);--luzmo-background-color-highlight-down: color-mix(in oklch, var(--luzmo-background-color-highlight), black 45%);--luzmo-background-color-highlight-focus: color-mix(in oklch, var(--luzmo-background-color-highlight), black 25%);--luzmo-background-color-alt-1: rgb(250, 250, 250);--luzmo-background-color-alt-2: rgb(239, 239, 239);--luzmo-border-width: 1px;--luzmo-font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen-Sans, Ubuntu, Cantarell, 'Helvetica Neue', Helvetica, Arial, sans-serif;--luzmo-font-size-xs: 10px;--luzmo-font-size-s: 12px;--luzmo-font-size-m: 14px;--luzmo-font-size: 14px;--luzmo-font-size-l: 16px;--luzmo-font-size-xl: 18px;--luzmo-font-size-xxl: 20px;--luzmo-font-style: normal;--luzmo-line-height: normal;--luzmo-font-weight: 400;--luzmo-font-weight-semibold: 500;--luzmo-font-weight-bold: 600;--luzmo-font-color: #333;--luzmo-font-color-hard: #000;--luzmo-font-color-disabled: var(--luzmo-color-disabled);--luzmo-font-color-extra-dimmed: #888;--luzmo-font-color-hover: color-mix(in oklch, var(--luzmo-font-color), black 8%);--luzmo-font-color-down: color-mix(in oklch, var(--luzmo-font-color), black 20%);--luzmo-font-color-focus: color-mix(in oklch, var(--luzmo-font-color), black 8%);--luzmo-scrollbar-size: 6px;--luzmo-scrollbar-width: thin;--luzmo-scrollbar-track-background: transparent;--luzmo-scrollbar-track-border-radius: var(--luzmo-border-radius-s);--luzmo-scrollbar-thumb-background: rgba(var(--luzmo-border-color-rgb), 0.3);--luzmo-scrollbar-thumb-border-radius: var(--luzmo-border-radius-s);--luzmo-scrollbar-thumb-hover-background: rgba(var(--luzmo-border-color-rgb), 0.4);--luzmo-primary: #4434ff;--luzmo-primary-hover: color-mix(in oklch, var(--luzmo-primary), black 8%);--luzmo-primary-down: color-mix(in oklch, var(--luzmo-primary), black 20%);--luzmo-primary-focus: color-mix(in oklch, var(--luzmo-primary), black 8%);--luzmo-primary-inverse-color: #ffffff;--luzmo-primary-rgb: 68, 52, 255;--luzmo-secondary: #ff00ff;--luzmo-secondary-hover: color-mix(in oklch, var(--luzmo-secondary), black 8%);--luzmo-secondary-down: color-mix(in oklch, var(--luzmo-secondary), black 20%);--luzmo-secondary-focus: color-mix(in oklch, var(--luzmo-secondary), black 8%);--luzmo-secondary-inverse-color: #ffffff;--luzmo-secondary-rgb: 255, 0, 255;--luzmo-secondary-outline: rgba(255, 0, 255, 0.2);--luzmo-negative-color: #ca221c;--luzmo-negative-color-hover: color-mix(in oklch, var(--luzmo-negative-color), black 8%);--luzmo-negative-color-down: color-mix(in oklch, var(--luzmo-negative-color), black 20%);--luzmo-negative-color-focus: color-mix(in oklch, var(--luzmo-negative-color), black 8%);--luzmo-negative-color-rgb: 202, 34, 28;--luzmo-positive-color: rgb(20, 150, 101);--luzmo-positive-color-hover: color-mix(in oklch, var(--luzmo-positive-color), black 8%);--luzmo-positive-color-down: color-mix(in oklch, var(--luzmo-positive-color), black 20%);--luzmo-positive-color-focus: color-mix(in oklch, var(--luzmo-positive-color), black 8%);--luzmo-positive-color-rgb: 20, 150, 101;--luzmo-selected-color: rgb(110, 110, 110);--luzmo-selected-color-hover: color-mix(in oklch, var(--luzmo-selected-color), black 25%);--luzmo-selected-color-down: color-mix(in oklch, var(--luzmo-selected-color), black 45%);--luzmo-selected-color-focus: color-mix(in oklch, var(--luzmo-selected-color), black 25%);--luzmo-selected-color-hard: #1e1e1e;--luzmo-selected-color-hard-hover: color-mix(in oklch, var(--luzmo-selected-color-hard), black 25%);--luzmo-selected-color-hard-down: color-mix(in oklch, var(--luzmo-selected-color-hard), black 45%);--luzmo-selected-color-hard-focus: color-mix(in oklch, var(--luzmo-selected-color-hard), black 25%);--luzmo-color-informative: #1a77e9;--luzmo-color-informative-rgb: 26, 119, 233;--luzmo-color-disabled: #aaaaaa;--luzmo-spacing-1: 2px;--luzmo-spacing-2: 4px;--luzmo-spacing-3: 8px;--luzmo-spacing-4: 12px;--luzmo-spacing-5: 16px;--luzmo-indicator-gap: 2px;--luzmo-indicator-width: 1px;--luzmo-indicator-color: var(--luzmo-primary);--luzmo-component-height-xxs: 20px;--luzmo-component-height-xs: 24px;--luzmo-component-height-s: 28px;--luzmo-component-height: 32px;--luzmo-component-height-l: 40px;--luzmo-component-height-xl: 48px;--luzmo-component-height-xxl: 64px;--luzmo-icon-size-xxs: 12px;--luzmo-icon-size-xs: 14px;--luzmo-icon-size-s: 16px;--luzmo-icon-size-m: 18px;--luzmo-icon-size-l: 20px;--luzmo-icon-size-xl: 22px;--luzmo-icon-size-xxl: 32px}", document.head.appendChild(e);
 	}
 })();
-import { C as e, S as t, T as n, _ as r, a as i, b as a, c as o, d as s, f as c, g as l, h as u, i as d, l as f, m as p, n as m, o as h, p as g, r as _, s as v, t as y, u as b, v as x, w as S, x as C, y as w } from "../ai-chat-BUiqA_bv.js";
+import { C as e, S as t, T as n, _ as r, a as i, b as a, c as o, d as s, f as c, g as l, h as u, i as d, l as f, m as p, n as m, o as h, p as g, r as _, s as v, t as y, u as b, v as x, w as S, x as C, y as w } from "../ai-chat-BYlVFmdP.js";
 export { d as AiChatSession, _ as AiChatSessionController, m as LuzmoAiChat, n as LuzmoAiChatEmptyState, r as buildAiPromptDeleteRequest, x as buildAiPromptProperties, w as buildAiPromptRequest, a as buildAnalystAiPromptProperties, C as buildDashboardAiPromptProperties, t as buildItemAiPromptProperties, e as chartToItemAsset, i as createAiChatSession, c as createInitialProgress, h as createInitialStreamState, v as createStreamHandler, b as extractChartFromChunk, s as extractDashboardFromChunk, p as fetchStreamingResponse, o as getAgentStreamDefinition, S as getAiPromptUrl, g as hasProgressChunk, y as isRecognizedStep, u as parseStreamLine, f as processStreamChunk, l as readNdjsonStream };