@telia-ace/widget-conversation-flamingo 1.0.14 → 1.0.37

package/README.md

@@ -1,490 +0,0 @@
-# Widget Conversation API
-
-The Widget Conversation API provides support for reading and writing to a conversational component inside a widget.
-
-## Sandbox
-
-For demonstration purposes, we've set up a sandbox for the Widget Conversational API so that you can see it in action. Keep in mind that this is for demonstration purposes only and may not reflect best practice.
-
-> We do not recommend binding functions to the `window` object.
-
-[![Edit elegant-jones-rnyrd](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/elegant-jones-rnyrd?fontsize=14&hidenavigation=1&theme=dark)
-
-## Accessing the API
-
-In order to access the API you need to have a widget with a conversational component.
-
-### Creating the plugin
-
-You need to register the conversational provider in the `providers`-property in the component. To access the global instance of `ConversationPlatform`, you pass in the current `Container` to the `getInstance()` method. It will return a `Promise` that is resolved to the `ConversationPlatform` instance. In the instance, register a provider and pass in name and handler by calling the `registerProvider()` function as shown below.
-
-The handler function will be called once a conversational component for the specified provider is activated in the widget. Use the provider to interact with the conversation.
-
-```ts
-import { ConversationPlatform } from '@telia-ace/widget-conversation';
-
-const MyPlugin = async (container) => {
-  const platform = await ConversationPlatform.getInstance(container);
-
-  platform.registerProvider('my-chat', (conversation, component) => {
-    // start interacting with the conversation here
-  });
-};
-```
-
-You also need to register the provider inside the widget configuration:
-
-```JSON
-   "my-conversation-component": {
-        "type": "conversation",
-        "properties": {
-            "providers": ["my-chat"],
-            // ...
-        },
-        "context": {}
-    },
-```
-
-### Creating an agent in the conversation
-
-When using `createAgent` you can specify both a name and an avatar. These will then be displayed in the conversation alongside that agent's entries.
-
-```ts
-const agent = conversation.createAgent({
-  name: 'Agent Smith',
-  avatar: 'https://www.site.com/avatar.jpg',
-});
-```
-
-## Writing to the conversation
-
-**`print()` accepts an array, which is considered best practice when writing to the conversation. The previous way of posting an object will still currently be supported, but is considered to be deprecated.**
-
-### Posting, updating and removing content
-
-When managing content in the conversation you'll first need to create an `Agent`-object and then use its `print()` function. There are serveral types of entries in order to accommodate different types of content.
-
-The `print(items: ConversationMessageItem[])` function let's you return a `ConversationEntry` message that can be used to update and/or remove the content from the conversation.
-
-##### Example of simple text message
-
-```ts
-// print user message
-conversation.user.print([['text', 'Lorem ipsum']]);
-
-// print agent message
-const agent = conversation.createAgent();
-agent.print([['text', 'Lorem ipsum']]);
-```
-
-##### Example of updating or removing content
-
-```ts
-const agent = conversation.createAgent();
-const entry = agent.print([['text', 'Hello world!']]);
-
-entry.update([
-  // ...
-]);
-
-entry.remove();
-```
-
-### Entry with list of actions
-
-You can post an entry into the conversation with actions. You can specify a title, body and available actions. This is only supported for the `Agent` and will be displayed as a system message.
-
-This can be either in the form of a "ButtonList" or an "LinkList" as demostrated below.
-
-| Name      | Type     | Description                                  |
-| --------- | -------- | -------------------------------------------- |
-| `header`  | `string` | Header for the entry.                        |
-| `actions` | `array`  | Array of of available actions for the entry. |
-
-##### Example of list of actions
-
-```ts
-// example of button list
-agent.print([
-  [
-    'button-list',
-    {
-      header: 'Download invoices',
-      actions: [
-        {
-          actionKey: 'invoice_190201',
-          label: 'Invoice 190201',
-        },
-        {
-          actionKey: 'invoice_190301',
-          label: 'Invoice 190301',
-        },
-      ],
-    },
-  ],
-]);
-
-// here we use a link list instead, but with the same actions
-agent.print([
-  [
-    'link-list',
-    {
-      header: 'Download invoices',
-      actions: [
-        {
-          actionKey: 'invoice_190201',
-          label: 'Invoice 190201',
-        },
-        {
-          actionKey: 'invoice_190301',
-          label: 'Invoice 190301',
-        },
-      ],
-    },
-  ],
-]);
-
-// and an item list could contain an optional icon and description
-agent.print([
-  [
-    'item-list',
-    {
-      header: 'Download invoices',
-      actions: [
-        {
-          actionKey: 'invoice_190201',
-          label: 'Invoice 190201',
-          symbol: {
-            type: 'FontAwesome',
-            content: 'file',
-          },
-        },
-        {
-          actionKey: 'invoice_190301',
-          label: 'Invoice 190301',
-          description: 'Clicking here will download the invoice',
-        },
-      ],
-    },
-  ],
-]);
-```
-
-### Entry with a form
-
-You can also post a message with a form attached. This uses the `FormBuilder`-method. This is handled by the `conversation.form` event. It is only supported for `Agent` and will be displayed as a system message.
-
-| Name    | Type                    | Description                                                                                                                                                                                  |
-| ------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `title` | `string`                | Title for the entry.                                                                                                                                                                         |
-| `body`  | `string`                | Body content for the entry. Supports HTML.                                                                                                                                                   |
-| `form`  | `(FormBuilder) => void` | A callback function for building the form. Refer to the [`@telia-ace/widget-forms`](https://www.npmjs.com/package/@telia-ace/widget-forms) package for more information about `FormBuilder`. |
-| `key`   | `string`                | The key used to refer to the form when validating and submitting the form.                                                                                                                   |
-
-##### Example of an entry with a form
-
-```ts
-agent.print({
-  title: 'Log in',
-  body: 'Enter your ID to login',
-  key: 'my-login-form',
-  form: (builder) => {
-    builder
-      .createComponent({
-        component: 'Text',
-        type: 'number',
-        name: 'id',
-        title: 'ID',
-        required: true,
-      })
-      .createComponent({
-        title: 'Log in',
-        actionKey: 'submit',
-        name: 'submit',
-        component: 'Submit',
-        type: 'submit',
-        evaluate: true,
-        value: 'Log in',
-      });
-  },
-});
-```
-
-### Entry with a video call
-
-Use the `video-request` item type to create an entry representing an incoming video call. This entry can also have a form attached, which uses the `FormBuilder`-method and is handled by the `conversation.form` event. It is only supported for an `Agent` and will be displayed as a system message.
-
-| Name           | Type     | Description                                     |
-| -------------- | -------- | ----------------------------------------------- |
-| `header`       | `string` | Header for the entry.                           |
-| `acceptLabel`  | `string` | Label to be shown for the "accept call button"  |
-| `declineLabel` | `string` | Label to be shown for the "decline call button" |
-
-##### Example of an entry for an incoming video call
-
-```ts
-agent.print([
-  [
-    'video-request',
-    {
-      header: 'Video call',
-      accept: 'Accept',
-      decline: 'Decline',
-    },
-  ],
-]);
-```
-
-When the user presses one of these buttons to accept or decline the call, an action will be dispatched with actionKey `accept-video-call` or `decline-video-call`, depending on which button was clicked.
-
-Listening to these actions can be done as following:
-
-```ts
-component.actions.watch('conversation.action', (input, next) => {
-  if (input.actionKey === 'accept-video-call') {
-    // this will render an overlay over the widget,
-    // and prepare the widget for displaying the actual call
-    component.actions.dispatch('show-overlay', {});
-  } else if (input.actionKey === 'decline-video-call') {
-    // ...
-  }
-  return next(input);
-});
-```
-
-### Video Call Events
-
-| Action Key                  | Description                                                                                    |
-| --------------------------- | ---------------------------------------------------------------------------------------------- |
-| `show-overlay`              | Dispatch this event when you want to render an overlay where you can render the video call     |
-| `overlay-mounted`           | Dispatched when the overlay is rendered, will provide an HTML element to render the video call |
-| `hide-overlay`              | Hide overlay                                                                                   |
-| `show-overlay-conversation` | Show the underlying conversation on top of the video overlay                                   |
-| `hide-overlay-conversation` | Hide the conversation overlay.                                                                 |
-
-#### show-overlay
-
-This event is recommended to be used when a user accept an video call. See the example above for one way of implementing it. This event will result in the `overlay-mounted` event being dispatched, which you may subscribe to and use to render the video call.
-
-#### overlay-mounted
-
-Use an overlay over the conversation to render your video call. The `show-overlay`-action, as described above, accomplishes this. After the overlay is rendered and ready it will dispatch another event: `overlay-mounted`. Use the HTML element this generates to render your video call.
-
-```ts
-component.actions.watch('overlay-mounted', (overlayElem, next) => {
-  // the overlayElem here may be used to render the ongoing call
-});
-```
-
-#### hide-overlay
-
-Dispatching this event will hide the overlay
-
-```ts
-component.actions.dispatch('hide-overlay', {});
-```
-
-#### show-overlay-conversation
-
-Dispatching this event will show the underlying conversation on top of the video overlay.
-
-```ts
-component.actions.dispatch('show-overlay-conversation', {});
-```
-
-#### hide-overlay-conversation
-
-Dispatching this event will hide the conversation overlay.
-
-```ts
-component.actions.dispatch('hide-overlay-conversation', {});
-```
-
-### Available default messages types
-
-The below message types are available out of the box.
-
-| Message type key | Description                                                | Value                                                                                                                                         |
-| ---------------- | ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| `button-list`    | List of action buttons.                                    | `{ header?: string, actions: Array<{ actionKey: string, label: string, symbol?: { type: string, content: string } }> }      `                 |
-| `link-list`      | List of action links.                                      | `{ header?: string, actions: Array<{ actionKey: string, label: string }> }`                                                                   |
-| `item-list`      | List of detailed items with optional description and icon. | `{ header?: string, actions: Array<{ actionKey: string, label: string, description?: string, symbol?: { type: string, content: string } }> }` |
-| `html`           | Html content.                                              | `{ body: string }`                                                                                                                            |
-| `separator`      | Separator for dividing different messages.                 | N/A                                                                                                                                           |
-| `text`           | Plain text content.                                        | `string`                                                                                                                                      |
-| `video-request`  | Incoming video call prompt.                                | `{ header: string, accept: string, decline: string }`                                                                                         |
-
-### The loading and typing indicators
-
-When you need to fetch data from external resource you should use the `loading()` function on the `ConversationProvider` to inform the user that something is about to happen. Even in cases when the response is available immediately it gives a better user experience to present a loading indicator for a short while.
-
-When you need to make the user aware that your agent is currently typing, you should use the `typing` function on `Agent`.
-
-#### Example of `loading`
-
-```ts
-const done = conversation.loading();
-// ...
-done(); // remove loader
-```
-
-#### Example of `typing`
-
-```ts
-const done = agent.typing();
-// ...
-done(); // remove loader
-```
-
-## Writing system messages
-
-System message in the conversation are sent by using the `print` method on the `conversation`. The `print` method accepts the same arguments as on the `Agent`.
-
-#### Example
-
-```ts
-conversation.print([['text', 'Hello world!']]);
-```
-
-## Reading from the conversation
-
-The second parameter to your provider handler is a `ComponentNode` instance representing the conversational component. From it you can read the component's properties and react to action emitted by the component.
-
-The following actions are emitted from the conversational component:
-
-> For default actions it is necessary to call `next()` unless you want to completely stop the execution flow for the particular action. Not doing so will stop any succeeding handlers and may unintentionally break functionality.
-
-| Action                     | Name         | Type       | Description                                               |
-| -------------------------- | ------------ | ---------- | --------------------------------------------------------- |
-| `conversation.user-typing` | `textLength` | `number`   | The current text length of the user's message.            |
-| `conversation.user-submit` | `text`       | `string`   | The submitted text.                                       |
-| `conversation.action`      | `text`       | `string`   | Key of the submitted action.                              |
-| `conversation.form`        | `data`       | `FormData` | The form data.                                            |
-| `conversation.form`        | `formKey`    | `string`   | The unique key for the form.                              |
-| `conversation.form`        | `actionKey`  | `string`   | The key of the form component responsible for the change. |
-
-If you want to subscribe to any of the `conversation.form`-actions you have access to the `ComponentNodeController`. Example below:
-
-```ts
-component.actions.watch('conversation.form', (input, next) => {
-  return next(input);
-});
-```
-
-### Submitting forms
-
-If you want to listen for form events you should subscribe to the `conversation.form` event. By passing a `key` to the form, you are able to target the form in this listener.
-
-```ts
-component.actions.watch('conversation.form', (input, next) => {
-  if (input.formKey === 'my-login-form' && input.actionKey === 'submit') {
-    const username = input.data.username;
-    const password = input.data.password;
-  }
-
-  return next(input);
-});
-```
-
-### Adding custom list items
-
-You can add custom list items to the conversation. To do so you have to register your own custom React component, which will be mapped to a key also provided by you.
-
-#### Example of custom list items
-
-```ts
-import { registerCustomMessageComponent } from '@telia-ace/widget-conversation';
-
-registerCustomMessageComponent(
-  container,
-  'my-custom-list-item',
-  import('./my-custom-list-item')
-);
-```
-
-Once the component has been registered it will be available to be used as any other item in the `print` method on the Conversation API.
-
-## Custom secondary action
-
-You can add a secondary action button that's displayed next to the user input field. This button can run any event that you write. You need to add the `secondaryAction` property to the conversation component in the configuration. It accepts an object with the following properties:
-
-| Name     | Type     | Description                                                         |
-| -------- | -------- | ------------------------------------------------------------------- |
-| `action` | `string` | An action that will be dispatched when the button is pressed        |
-| `label`  | `string` | Will be used as a "title" and aria-label on the HTML button element |
-| `icon`   | `string` | An icon to be displayed, defaults to "browse" icon if left empty    |
-
-```json
-    "conversation": {
-        "type": "conversation",
-        "properties": {
-            "secondaryAction": {
-                "action": "my-secondary-action",
-                "label": "Label for the secondary action",
-                "icon": "my-icon"
-            }
-            // ...other properties
-        }
-    }
-```
-
-When you have added this property to the component, you can create an event for it in your code:
-
-```ts
-component.actions.watch('conversation.action', (input, next) => {
-  if (input === 'my-secondary-action') {
-    // handle action
-  }
-});
-```
-
-## Completing a conversation (handover)
-
-When you are handing over the conversation to another provider, the current provider is disabled until the child provider has completed. To hand it over to the previous provider you should use the `complete()` method on the `ConversationProvider` object.
-
-Example:
-
-```ts
-if (actionKey === 'email-confirmation-submit') {
-  conversation.complete();
-}
-```
-
-This will complete the current provider and return to the one that started the now closed provider.
-
-## Rehydrating the conversation
-
-The conversation may be stored in a session to allow it to remain when reloading the page.
-This behavior is disabled by default but can be turned on by adding the `rehydrate` property to the `ConversationComponent` like this:
-
-```
-"components": {
-    "type": "conversation",
-    "properties": {
-        "rehydrate": true
-    }
-}
-
-```
-
-## Reading the conversation history
-
-In order to print the complete conversation you can use the `ConversationProvider.getHistory()` method.
-
-Example:
-
-```ts
-const logs = conversation.getHistory();
-```
-
-This will produce an array of items in the following format:
-
-```ts
-{
-    message?: string;       // the body of the message, if any
-    options?: string[]      // an array of options presented in the message
-    alias: string;          // name of the message author
-    source: string;         // agent or user
-    timestamp: number;      // timestamp of when message was created
-}
-```

package/dist/agent.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"agent.d.ts","sourceRoot":"","sources":["../src/agent.ts"],"names":[],"mappings":"AACA,OAAO,EACL,iBAAiB,EAGlB,MAAM,2BAA2B,CAAC;AACnC,OAAO,EAAE,oBAAoB,EAAE,MAAM,yBAAyB,CAAC;AAC/D,OAAO,EAEL,2BAA2B,EAC3B,wBAAwB,EACxB,MAAM,EACP,MAAM,SAAS,CAAC;AAEjB,MAAM,MAAM,aAAa,GAAG;IAC1B,EAAE,CAAC,EAAE,MAAM,CAAC;IACZ,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;CAC1B,CAAC;AAEF,qBAAa,KAAK;IAMd,OAAO,CAAC,QAAQ;IALlB,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;gBAGf,QAAQ,EAAE,oBAAoB,EACtC,QAAQ,EAAE,aAAa;IAOzB,KAAK,aAEC,MAAM,GACN,2BAA2B,GAC3B,yBAAyB,GAAG,CAAC,GAC7B,yBAAyB,GAAG,CAAC,EAAE,YACzB;QACR,GAAG,CAAC,EAAE,MAAM,CAAC;KACd,KACA,iBAAiB,GAAG,SAAS,CAe9B;IACF,MAAM,iCAKJ;IAEF,MAAM,CAAC,QAAQ,EAAE,aAAa,GAAG,IAAI;CAkBtC"}

package/dist/components/conversation/conversation.d.ts

@@ -1,26 +0,0 @@
-import { LitElement, PropertyValueMap } from 'lit';
-import { Ref } from 'lit/directives/ref.js';
-import '@teliads/components/dist/components/telia-icon';
-import './ui/message';
-import './ui/message-list';
-/** Message types */
-import './ui/message-types/message-type-html';
-import './ui/message-types/message-type-link-list';
-import './ui/message-types/message-type-separator';
-declare const WidgetElement: (new (...args: any[]) => import("@telia-ace/widget-runtime-flamingo/dist/mixins/widget-component.mixin").WidgetComponentInterface) & typeof LitElement;
-export declare class ConversationComponent extends WidgetElement {
-    static styles: import("lit").CSSResultGroup[];
-    _onClick(e: Event): Promise<void>;
-    _onSendMessage(e: Event): Promise<void>;
-    _inputHandler(e: any): void;
-    _actionHandler(e: CustomEvent<{
-        actionKey: string;
-        payload: Record<string, any> | string;
-    }>): void;
-    message: string;
-    conversationContentRef: Ref<HTMLDivElement>;
-    updated(changedProperties: PropertyValueMap<any> | Map<PropertyKey, unknown>): void;
-    render(): import("lit").TemplateResult<1>;
-}
-export default ConversationComponent;
-//# sourceMappingURL=conversation.d.ts.map

package/dist/components/conversation/conversation.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"conversation.d.ts","sourceRoot":"","sources":["../../../src/components/conversation/conversation.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,gBAAgB,EAAsB,MAAM,KAAK,CAAC;AAEvE,OAAO,EAAa,GAAG,EAAO,MAAM,uBAAuB,CAAC;AAM5D,OAAO,gDAAgD,CAAC;AAKxD,OAAO,cAAc,CAAC;AACtB,OAAO,mBAAmB,CAAC;AAE3B,oBAAoB;AACpB,OAAO,sCAAsC,CAAC;AAC9C,OAAO,2CAA2C,CAAC;AACnD,OAAO,2CAA2C,CAAC;AAGnD,QAAA,MAAM,aAAa,wJAA8B,CAAC;AAElD,qBACa,qBAAsB,SAAQ,aAAa;IACtD,OAAgB,MAAM,iCAgIpB;IAEI,QAAQ,CAAC,CAAC,EAAE,KAAK;IAKjB,cAAc,CAAC,CAAC,EAAE,KAAK;IAO7B,aAAa,CAAC,CAAC,EAAE,GAAG;IAIpB,cAAc,CACZ,CAAC,EAAE,WAAW,CAAC;QAAE,SAAS,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,GAAG,MAAM,CAAA;KAAE,CAAC;IAM9E,OAAO,EAAE,MAAM,CAAM;IAErB,sBAAsB,EAAE,GAAG,CAAC,cAAc,CAAC,CAAe;IAEjD,OAAO,CACd,iBAAiB,EAAE,gBAAgB,CAAC,GAAG,CAAC,GAAG,GAAG,CAAC,WAAW,EAAE,OAAO,CAAC,GACnE,IAAI;IAcE,MAAM;CA6DhB;AAED,eAAe,qBAAqB,CAAC"}

package/dist/components/conversation/plugin.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"plugin.d.ts","sourceRoot":"","sources":["../../../src/components/conversation/plugin.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAEpD,OAAO,EACL,0BAA0B,EAC1B,yBAAyB,EAC1B,MAAM,aAAa,CAAC;AACrB,OAAO,EACL,mBAAmB,EACnB,uBAAuB,EACxB,MAAM,+BAA+B,CAAC;AAIvC,MAAM,MAAM,0BAA0B,GAAG;IACvC,SAAS,EAAE,MAAM,CAAC;IAClB,OAAO,EAAE,CAAC,qBAAqB,CAAC,CAAC;IACjC,MAAM,EAAE,yBAAyB,CAAC;IAClC,IAAI,EAAE,uBAAuB,CAAC;CAC/B,CAAC;AAEF,KAAK,qBAAqB,GAAG;IAC3B,GAAG,EAAE,MAAM,CAAC;CACb,GAAG,0BAA0B,CAAC;AAE/B,MAAM,MAAM,mBAAmB,GAAG;IAChC,OAAO,EAAE,OAAO,CAAC;IACjB,YAAY,EAAE,yBAAyB,EAAE,CAAC;IAC1C,QAAQ,EAAE,mBAAmB,EAAE,CAAC;CACjC,CAAC;AAuCF,MAAM,MAAM,+BAA+B,GAAG;IAC5C,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,QAAQ,EAAE,0BAA0B,EAAE,CAAC;IACvC,OAAO,CAAC,EAAE;QAAE,YAAY,EAAE,OAAO,CAAC;QAAC,SAAS,EAAE,OAAO,CAAA;KAAE,CAAC;IACxD,yBAAyB,CAAC,EAAE,MAAM,CAAC;IACnC,6BAA6B,CAAC,EAAE,MAAM,CAAC;IACvC,OAAO,EAAE,OAAO,CAAC;IACjB,gBAAgB,EAAE,MAAM,CAAC;IACzB,aAAa,EAAE,OAAO,CAAC;IACvB,WAAW,EAAE,OAAO,CAAC;IACrB,cAAc,EAAE,OAAO,CAAC;IACxB,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,SAAS,EAAE,MAAM,CAAC;IAClB,UAAU,EAAE,MAAM,CAAC;IACnB,YAAY,EAAE,GAAG,EAAE,CAAC;IACpB,wBAAwB,CAAC,EAAE,MAAM,CAAC;IAClC,eAAe,EAAE,MAAM,CAAC;IACxB,eAAe,CAAC,EAAE;QAAE,IAAI,CAAC,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC;CACpE,CAAC;AAEF,eAAO,MAAM,qBAAqB,cAAqB,SAAS,kBAkI/D,CAAC;AAEF,eAAe,qBAAqB,CAAC"}

package/dist/components/conversation/ui/message-list.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"message-list.d.ts","sourceRoot":"","sources":["../../../../src/components/conversation/ui/message-list.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAsB,MAAM,KAAK,CAAC;AAErD,OAAO,EAAE,wBAAwB,EAAE,MAAM,gBAAgB,CAAC;AAE1D,qBACa,WAAY,SAAQ,UAAU;IACzC,OAAgB,MAAM,0BAapB;IAGF,KAAK,EAAE,wBAAwB,CAAC,GAAG,CAAC,EAAE,CAAM;IAE5C,OAAO,CAAC,kBAAkB;IAI1B,OAAO,CAAC,sBAAsB;IAWrB,MAAM;CA4BhB"}

package/dist/components/conversation/ui/message-types/message-type-html.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"message-type-html.d.ts","sourceRoot":"","sources":["../../../../../src/components/conversation/ui/message-types/message-type-html.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAa,MAAM,KAAK,CAAC;AAG5C,OAAO,EACL,+BAA+B,EAC/B,wBAAwB,EACzB,MAAM,mBAAmB,CAAC;AAE3B,qBACa,eAAgB,SAAQ,UAAU;IAC7C,OAAgB,MAAM,4BAcpB;IAGF,OAAO,EAAG,wBAAwB,CAAC,+BAA+B,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,CAAC;IAErE,MAAM;CAKhB"}

package/dist/components/conversation/ui/message-types/message-type-link-list.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"message-type-link-list.d.ts","sourceRoot":"","sources":["../../../../../src/components/conversation/ui/message-types/message-type-link-list.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAsB,MAAM,KAAK,CAAC;AAErD,OAAO,EACL,+BAA+B,EAC/B,wBAAwB,EACzB,MAAM,mBAAmB,CAAC;AAE3B,qBACa,mBAAoB,SAAQ,UAAU;IACjD,OAAgB,MAAM,4BAyCpB;IAGF,OAAO,EAAG,wBAAwB,CAAC,+BAA+B,CAAC,QAAQ,CAAC,CAAC,GAAG,CAAC,CAAC;IAElF,YAAY,CAAC,IAAI,EAAE,GAAG;IAYb,MAAM;CAkBhB"}

package/dist/components/conversation/ui/message-types/message-type-separator.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"message-type-separator.d.ts","sourceRoot":"","sources":["../../../../../src/components/conversation/ui/message-types/message-type-separator.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAa,MAAM,KAAK,CAAC;AAE5C,OAAO,EACL,+BAA+B,EAC/B,wBAAwB,EACzB,MAAM,mBAAmB,CAAC;AAE3B,qBACa,oBAAqB,SAAQ,UAAU;IAClD,OAAgB,MAAM,4BAapB;IAGF,OAAO,EAAG,wBAAwB,CAAC,+BAA+B,CAAC,SAAS,CAAC,CAAC,GAAG,CAAC,CAAC;IAE1E,MAAM;CAGhB"}

package/dist/components/conversation/ui/message.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"message.d.ts","sourceRoot":"","sources":["../../../../src/components/conversation/ui/message.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAa,OAAO,EAAE,MAAM,KAAK,CAAC;AAGrD,OAAO,EAAE,0BAA0B,EAAE,MAAM,WAAW,CAAC;AAGvD,qBACa,OAAQ,SAAQ,UAAU;IACrC,OAAgB,MAAM,0BAmFpB;IAGF,OAAO,EAAG,0BAA0B,CAAC;IAErC,gBAAgB,CAAC,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,GAAG,IAAI;IA0B9C,MAAM;CA2DhB"}

package/dist/components/conversation/utils.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"utils.d.ts","sourceRoot":"","sources":["../../../src/components/conversation/utils.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,4BAA4B,SAAU,WAAW,SAQ7D,CAAC"}