@limetech/lime-elements 36.3.1-next.2 → 36.3.1

package/dist/collection/components/chip-set/chip-set.js

@@ -85,7 +85,6 @@ export class ChipSet {
   }
   /**
    * Used to find out whether the chip-set is in edit mode.
-   *
    * @returns {Promise<boolean>} `true` if the chip-set is in edit mode, `false` otherwise.
    */
   async getEditMode() {
@@ -93,7 +92,6 @@ export class ChipSet {
   }
   /**
    * Used to set focus to the chip-set input field.
-   *
    * @param {boolean} emptyInput if `true`, any text in the input is discarded
    * @returns {Promise<void>} does not return anything, but methods have to be async
    */
@@ -111,7 +109,6 @@ export class ChipSet {
   /**
    * Used to empty the input field. Used in conjunction with `emptyInputOnBlur` to let the
    * consumer control when the input is emptied.
-   *
    * @returns {Promise<void>} does not return anything, but methods have to be async
    */
   async emptyInput() {
@@ -240,7 +237,6 @@ export class ChipSet {
   }
   /**
    * Enter edit mode when the text field receives focus. When editMode is true, the input element will be visible
-   *
    * @returns {void}
    */
   handleTextFieldFocus() {
@@ -256,7 +252,6 @@ export class ChipSet {
   /**
    * Exit edit mode when the input element loses focus. This makes sure the input element does not take up any
    * additional space when the user it not typing anything
-   *
    * @returns {void}
    */
   handleInputBlur() {

package/dist/collection/components/circular-progress/circular-progress.js

@@ -18,7 +18,6 @@ const PERCENT = 100;
  * Of course such numbers, if bigger than `maxValue` will be visualized as a
  * full progress.
  * :::
- *
  * @exampleComponent limel-example-circular-progress
  * @exampleComponent limel-example-circular-progress-sizes
  * @exampleComponent limel-example-circular-progress-props

package/dist/collection/components/code-editor/code-editor.js

@@ -10,8 +10,7 @@ import 'codemirror/addon/fold/brace-fold';
 import jslint from 'jsonlint-mod';
 /**
  * Currently this component support syntax highlighting for `javascript`,
- `json` and `typescript` formats.
- *
+ * `json` and `typescript` formats.
  * @exampleComponent limel-example-code-editor
  * @exampleComponent limel-example-code-editor-readonly-with-line-numbers
  * @exampleComponent limel-example-code-editor-fold-lint

package/dist/collection/components/color-picker/color-picker.js

@@ -10,7 +10,6 @@ import { h } from '@stencil/core';
  * :::note
  * Make sure to read our [guidelines about usage of colors](/#/DesignGuidelines/color-system.md/) from our palette.
  * :::
- *
  * @exampleComponent limel-example-color-picker
  * @exampleComponent limel-example-color-picker-readonly
  */

package/dist/collection/components/date-picker/flatpickr-adapter/flatpickr-adapter.js

@@ -11,7 +11,6 @@ import { YearPicker } from '../pickers/YearPicker';
  * This component is internal and only supposed to be used by
  * the limel-date-picker. This component is needed in order for us
  * to render the flatpickr calendar in a portal.
- *
  * @private
  */
 export class DatePickerCalendar {

package/dist/collection/components/dialog/dialog.js

@@ -19,7 +19,6 @@ import { createRandomString } from '../../util/random-string';
  * you should use the [DialogService](https://lundalogik.github.io/lime-web-components/versions/latest/#/api/dialog-service)
  * from Lime Web Components to open dialogs in Lime CRM.
  * :::
- *
  * @exampleComponent limel-example-dialog
  * @exampleComponent limel-example-dialog-nested-close-events
  * @exampleComponent limel-example-dialog-heading

package/dist/collection/components/file/file.js

@@ -20,7 +20,7 @@ const DEFAULT_FILE_CHIP = {
  * visual design including the upload icon hints end-users that this is not a
  * normal input field like other fields in the form for example.
  *
- *:::important
+ * :::important
  * you need to use a descriptive `label` that clarifies the
  * functionality of the file picker, and/or provides users with clear
  * instructions.
@@ -36,8 +36,7 @@ const DEFAULT_FILE_CHIP = {
  * - Choose a file
  *
  * and similar phrases...
- *:::
- *
+ * :::
  * @exampleComponent limel-example-file
  * @exampleComponent limel-example-file-custom-icon
  * @exampleComponent limel-example-file-accepted-types

package/dist/collection/components/flex-container/flex-container.js

@@ -3,7 +3,6 @@ import { h } from '@stencil/core';
  * This component is deprecated and will be removed in a future version of
  * Lime Elements. Please use CSS for your flexible container needs 🙂
  * https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Basic_Concepts_of_Flexbox
- *
  * @deprecated
  * @private
  * @slot - Container content

package/dist/collection/components/form/adapters/base-adapter.js

@@ -7,7 +7,6 @@ import { isNil, isNumber, isString, isBoolean, pickBy, negate, kebabCase, mapKey
  * the real definition of a primitive in javascript. In this context, primitive
  * really means "can be properly rendered to the dom by react". It just so
  * happens that react can render most primitives to the dom correctly.
- *
  * @see https://developer.mozilla.org/en-US/docs/Glossary/Primitive
  * @param {any} value the value to check
  * @returns {boolean} Whether or not the value is primitive
@@ -43,7 +42,6 @@ export class LimeElementsAdapter extends React.Component {
   /**
    * Given a key a value set the value of property named `key` to
    * the value of `value`
-   *
    * @param {string} key The name of the property
    * @param {any} value The value of the property
    * @returns {void}
@@ -57,7 +55,6 @@ export class LimeElementsAdapter extends React.Component {
    *
    * Events must be bound using this function otherwise events will bubble up too far
    * since react events are different that native dom events
-   *
    * @param {string} eventName the name of the event to get the handler for
    * @returns {any} the handler to bind to the component for the event name
    */
@@ -70,7 +67,6 @@ export class LimeElementsAdapter extends React.Component {
   }
   /**
    * Set events on the web component
-   *
    * @param {object} events Event names to handlers
    * @returns {void}
    */
@@ -82,7 +78,6 @@ export class LimeElementsAdapter extends React.Component {
   }
   /**
    * Remove events on the web component
-   *
    * @param {object} events Event names to handlers
    * @returns {void}
    */
@@ -94,7 +89,6 @@ export class LimeElementsAdapter extends React.Component {
   }
   /**
    * Get the events to remove from the component
-   *
    * @param {object} prevEvents previous events
    * @param {object} nextEvents new events
    * @returns {object} the events to remove
@@ -104,7 +98,6 @@ export class LimeElementsAdapter extends React.Component {
   }
   /**
    * Get the events to add to the component
-   *
    * @param {object} prevEvents previous events
    * @param {object} nextEvents new events
    * @returns {object} the events to add
@@ -116,7 +109,6 @@ export class LimeElementsAdapter extends React.Component {
    * Detect if event handlers have changed. If they
    * have changed, store them in the state, and remove and
    * re-add the changed event handlers
-   *
    * @returns {void}
    */
   updateEvents() {
@@ -141,7 +133,6 @@ export class LimeElementsAdapter extends React.Component {
   }
   /**
    * Get non primitive props. i.e. object, function, array, etc
-   *
    * @param {object} elementProps the props to pass the webcomponet
    * @returns {object} non primitive props
    */
@@ -150,7 +141,6 @@ export class LimeElementsAdapter extends React.Component {
   }
   /**
    * Get primitive props. i.e. integer, boolean, etc
-   *
    * @param {object} elementProps the props to pass the webcomponet
    * @returns {object} primitive props
    */
@@ -161,7 +151,6 @@ export class LimeElementsAdapter extends React.Component {
    * Given the previous renders props and the next renders props,
    * check if any of the property values have changed and return an
    * object with only those values
-   *
    * @param {object} prevNonPrimitiveProps the previous renders non primitive props
    * @param {object} nextNonPrimitiveProps the current renders non primitive props
    * @returns {object} the changed primitive props
@@ -176,7 +165,6 @@ export class LimeElementsAdapter extends React.Component {
    * instead of passing them as props the the React.createElement
    * function because non primitive props are not passed properly to the web
    * component via React.createElement
-   *
    * @param {object} elementProps element props to set
    * @returns {void}
    */

package/dist/collection/components/form/fields/field-helpers.js

@@ -3,7 +3,6 @@ import { retrieveSchema, ADDITIONAL_PROPERTY_FLAG } from '@rjsf/core/lib/utils';
 /**
  * Given two objects, get a list of keys for each value that is different between
  * the two objects. Compares using deep comparison
- *
  * @param {object} a first object
  * @param {object} b second object
  * @returns {any[]} the array of keys
@@ -19,7 +18,6 @@ const getDifferentKeys = (a = {}, b = {}) => {
  * has any other fields that are dependent on it, and if so reset those dependent fields
  * (by deleting them from the data so that their defaults are populated on the next rerender).
  * Call onChange with the updated data
- *
  * @param {any} oldData The previous data before a data change event
  * @param {any} newData The form data from a change event
  * @param {object} schema The schema associated with the data
@@ -52,7 +50,6 @@ export const resetDependentFields = (oldData, newData, schema, rootSchema) => {
 };
 /**
  * Check if the schema is of type object and have no declared properties
- *
  * @param {any} schema the schema
  * @returns {boolean} true if the schema is for a custom object
  */

package/dist/collection/components/form/fields/schema-field.js

@@ -23,7 +23,6 @@ import { FieldTemplate } from '../templates';
  * from the form data I would delete all the text from the name input field. Web components would emit this empty value
  * as '' or null. If the web component tries to emit `undefined`, null would be emitted instead because CustomEvent has
  * a default `detail` value of null
- *
  * @param {any} value the value associated with the schema
  * @param {any} schema the schema for the value
  * @returns {boolean} whether or not null should be changed to undefined
@@ -52,7 +51,6 @@ const getCustomComponent = (schema) => {
 };
 /**
  * Create properties from the factory that is set on `limel-form`
- *
  * @param {*} formContext the form context
  * @param {*} schema the schema for the current field
  * @returns {object} the properties created by the factory
@@ -178,7 +176,6 @@ export class SchemaField extends React.Component {
   }
   /**
    * Gets the path to the current property within the schema
-   *
    * @param {string} schemaId the id of the schema
    * @returns {string[]} an array with the schema path for the current property
    * @example

package/dist/collection/components/form/templates/common.js

@@ -19,7 +19,6 @@ export function renderDescription(description) {
  * If an object has the key 'title' it will have priority, followed by the key 'name'.
  * If 'title' nor 'name' is found, a required item will be considered.
  * Otherwise the first occurrence of a nonempty string is chosen.
- *
  * @param {*} data the data to find the title for
  * @param {*} fieldSchema schema for the item
  * @param {*} formSchema schema for the form

package/dist/collection/components/grid/grid.js

@@ -3,7 +3,6 @@ import { h } from '@stencil/core';
  * The `limel-grid` component creates a grid which can be used to control the
  * layout of other components. It uses CSS [grid-template-areas](https://developer.mozilla.org/en-US/docs/Web/CSS/grid-template-areas)
  * to enable easy configuration of its child-elements.
- *
  * @exampleComponent limel-example-grid
  * @slot - Grid content
  */

package/dist/collection/components/header/header.js

@@ -38,7 +38,6 @@ import { h } from '@stencil/core';
  * Background colors behind icons make them look like "call to action" buttons
  * and take a lot of attention from users.
  * :::
- *
  * @exampleComponent limel-example-header
  * @exampleComponent limel-example-header-colors
  * @exampleComponent limel-example-header-responsive

package/dist/collection/components/helper-line/helper-line.js

@@ -19,7 +19,6 @@ import { Host, h } from '@stencil/core';
  * However, to be more resourceful, the parent component can choose not
  * to render the helper-line as well.
  * :::
- *
  * @exampleComponent limel-example-helper-line
  * @exampleComponent limel-example-helper-line-invalid
  * @exampleComponent limel-example-helper-line-long-text

package/dist/collection/components/icon/icon.js

@@ -51,7 +51,6 @@ import iconCache from '../../global/icon-cache';
  * Search for an icon and **click on it to copy its name to clipboard**.
  *
  * <limel-example-icon-finder />
- *
  * @exampleComponent limel-example-icon
  * @exampleComponent limel-example-icon-background
  */
@@ -76,7 +75,6 @@ export class Icon {
   }
   /**
    * Load the SVG data for the icon from the icon cache
-   *
    * @param {string} name name of the icon
    * @returns {string} the icon SVG data
    */

package/dist/collection/components/info-tile/info-tile.js

@@ -7,7 +7,6 @@ import { h } from '@stencil/core';
  * If clicking on the component should navigate the user to
  * a new screen or web page, you need to provide a URL,
  * using the `link` property.
- *
  * @exampleComponent limel-example-info-tile
  * @exampleComponent limel-example-info-tile-badge
  * @exampleComponent limel-example-info-tile-progress

package/dist/collection/components/input-field/input-field.js

@@ -278,7 +278,6 @@ export class InputField {
     /**
      * Key handler for the input field
      * Will change focus to the first/last item in the dropdown list to enable selection with the keyboard
-     *
      * @param {KeyboardEvent} event event
      * @returns {void}
      */

package/dist/collection/components/list/list-renderer.js

@@ -12,7 +12,6 @@ export class ListRenderer {
      * and return the index at which that ListItem is located in `items`.
      * Returns `undefined` if no item should have the attribute set.
      * See https://github.com/material-components/material-components-web/tree/e66a43a75fef4f9179e24856649518e15e279a04/packages/mdc-list#accessibility
-     *
      * @param {Array<ListItem | ListSeparator>} items the items of the list, including any `ListSeparator`:s
      * @returns {number} the index as per the description
      */
@@ -39,7 +38,6 @@ export class ListRenderer {
     };
     /**
      * Render a single list item
-     *
      * @param {ListItem | ListSeparator} item the item to render
      * @param {number} index the index the item had in the `items` array
      * @returns {HTMLElement} the list item
@@ -69,7 +67,6 @@ export class ListRenderer {
     };
     /**
      * Render the text of the list item
-     *
      * @param {ListItem} item the list item
      * @returns {HTMLElement | string} the text for the list item
      */
@@ -84,7 +81,6 @@ export class ListRenderer {
     };
     /**
      * Render an icon for a list item
-     *
      * @param {ListRendererConfig} config the config object, passed on from the `renderListItem` function
      * @param {ListItem} item the list item
      * @returns {HTMLElement} the icon element

package/dist/collection/components/menu-list/menu-list-renderer.js

@@ -10,7 +10,6 @@ export class MenuListRenderer {
      * and return the index at which that MenuItem is located in `items`.
      * Returns `undefined` if no item should have the attribute set.
      * See https://github.com/material-components/material-components-web/tree/e66a43a75fef4f9179e24856649518e15e279a04/packages/mdc-list#accessibility
-     *
      * @param {Array<MenuItem | ListSeparator>} items the items of the list, including any `ListSeparator`:s
      * @returns {number} the index as per the description
      */
@@ -37,7 +36,6 @@ export class MenuListRenderer {
     };
     /**
      * Render a single list item
-     *
      * @param {MenuItem | ListSeparator} item the item to render
      * @param {number} index the index the item had in the `items` array
      * @returns {HTMLElement} the list item
@@ -59,7 +57,6 @@ export class MenuListRenderer {
     };
     /**
      * Render the text of the list item
-     *
      * @param {MenuItem} item the list item
      * @returns {HTMLElement | string} the text for the list item
      */
@@ -83,7 +80,6 @@ export class MenuListRenderer {
     };
     /**
      * Render an icon for a list item
-     *
      * @param {MenuListRendererConfig} config the config object, passed on from the `renderMenuItem` function
      * @param {MenuItem} item the list item
      * @returns {HTMLElement} the icon element

package/dist/collection/components/picker/picker.js

@@ -120,7 +120,6 @@ export class Picker {
   /**
    * Renders the dropdown with the items to pick from, or a spinner if the picker
    * is waiting for items to be received
-   *
    * @returns {HTMLElement} picker dropdown
    */
   renderDropdown() {
@@ -179,7 +178,6 @@ export class Picker {
   /**
    * Returns true if the picker is "full"
    * The picker is considered to be full if it has a value and only one is allowed
-   *
    * @returns {boolean} true if the picker is full
    */
   isFull() {
@@ -232,7 +230,6 @@ export class Picker {
   }
   /**
    * Check if a descendant still has focus. If not, reset text value and search result.
-   *
    * @returns {void}
    */
   handleStopEditAndBlur() {
@@ -248,7 +245,6 @@ export class Picker {
   }
   /**
    * Input handler for the input field
-   *
    * @param {InputEvent} event event
    * @returns {void}
    */
@@ -264,7 +260,6 @@ export class Picker {
   }
   /**
    * Change handler for the list
-   *
    * @param {LimelListCustomEvent<ListItem>} event event
    * @returns {void}
    */
@@ -285,7 +280,6 @@ export class Picker {
   }
   /**
    * Change handler for the list
-   *
    * @param {LimelChipSetCustomEvent} event event
    * @returns {void}
    */
@@ -300,7 +294,6 @@ export class Picker {
   /**
    * Focus handler for the chip set
    * Prevent focus if the picker has a value and does not support multiple values
-   *
    * @returns {void}
    */
   async handleInputFieldFocus() {
@@ -329,7 +322,6 @@ export class Picker {
   /**
    * Key handler for the input field
    * Will change focus to the first/last item in the dropdown list to enable selection with the keyboard
-   *
    * @param {KeyboardEvent} event event
    * @returns {void}
    */
@@ -360,7 +352,6 @@ export class Picker {
   }
   /**
    * Key handler for the dropdown
-   *
    * @param {KeyboardEvent} event event
    * @returns {void}
    */

package/dist/collection/components/popover/popover.js

@@ -49,8 +49,6 @@ import { ESCAPE } from '../../util/keycodes';
  * Do not make a popover too big. They should never take over the entire screen.
  * If your content is that big, you should probably be using a Modal instead.
  * :::
- *
- *
  * @slot - Content to put inside the surface
  * @exampleComponent limel-example-popover
  */

package/dist/collection/components/portal/contains.js

@@ -3,7 +3,6 @@
  *
  * If the child element is a descendant of a limel-portal, this function will
  * go back through the portal and check the original tree recursively
- *
  * @param {HTMLElement} element the parent element
  * @param {HTMLElement} child the child element to check
  * @returns {boolean} `true` if child is a descendant of element, taking

package/dist/collection/components/portal/portal.js

@@ -8,20 +8,19 @@ import { createPopper, } from '@popperjs/core';
  * There are some caveats when using this component
  *
  * Events might not bubble up as expected since the content is moved out to
- *   another DOM node.
+ * another DOM node.
  * Any styling that is applied to content from the parent will be lost, if the
- *   content is just another web compoent it will work without any issues.
- *   Alternatively, use the
- *   `style=""` html attribute.
+ * content is just another web compoent it will work without any issues.
+ * Alternatively, use the
+ * `style=""` html attribute.
  * Any component that is placed inside the container must have a style of
- *   `max-height: inherit`. This ensures that its placement is calculated
- *   correctly in relation to the trigger, and that it never covers its own
- *   trigger.
+ * `max-height: inherit`. This ensures that its placement is calculated
+ * correctly in relation to the trigger, and that it never covers its own
+ * trigger.
  * When the node is moved in the DOM, `disconnectedCallback` and
- *   `connectedCallback` will be invoked, so if `disconnectedCallback` is used
- *   to do any tear-down, the appropriate setup will have to be done again on
- *   `connectedCallback`.
- *
+ * `connectedCallback` will be invoked, so if `disconnectedCallback` is used
+ * to do any tear-down, the appropriate setup will have to be done again on
+ * `connectedCallback`.
  * @slot - Content to put inside the portal
  * @private
  * @exampleComponent limel-example-portal

package/dist/collection/components/shortcut/shortcut.js

@@ -7,7 +7,6 @@ import { h } from '@stencil/core';
  * By default, this navigation will happen within the same browser tab.
  * However, it is possible to override that behavior, by specifying a `target`
  * for the `link` property
- *
  * @exampleComponent limel-example-shortcut
  * @exampleComponent limel-example-shortcut-notification
  * @exampleComponent limel-example-shortcut-styling

package/dist/collection/components/snackbar/snackbar.js

@@ -2,12 +2,34 @@ import { MDCSnackbar } from '@material/snackbar';
 import { h, } from '@stencil/core';
 import translate from '../../global/translations';
 /**
+ * A Snackbar –also known as "Toast"– is used to inform the end user
+ * about an action or a process in the system.
+ * The information could vary from announcing that a process has just started,
+ * is taking place now, has ended, or has been interrupted or canceled.
+ *
+ * The information that you provide using a snackbar should be:
+ * - temporary
+ * - contextual
+ * - short
+ * - and most importantly, ignorable.
+ *
+ * It means if the user misses the information, it shouldn't be a big deal.
+ *
+ * :::note
+ * If the information you want to display has a higher importance or priority,
+ * and you need to make sure that the user takes an action to dismiss it,
+ * consider using the [Banner](/#/component/limel-banner/) component instead.
+ * For more complex interactions and for delivering more detailed information,
+ * [Dialog](/#/component/limel-dialog/) is a better choice.
+ * :::
  * @exampleComponent limel-example-snackbar
+ * @exampleComponent limel-example-snackbar-with-action
+ * @exampleComponent limel-example-snackbar-with-changing-messages
  */
 export class Snackbar {
   constructor() {
     this.message = undefined;
-    this.timeout = undefined;
+    this.timeout = 5000;
     this.actionText = undefined;
     this.dismissible = undefined;
     this.multiline = undefined;
@@ -115,13 +137,14 @@ export class Snackbar {
           "references": {}
         },
         "required": false,
-        "optional": false,
+        "optional": true,
         "docs": {
           "tags": [],
           "text": "The amount of time in milliseconds to show the snackbar."
         },
         "attribute": "timeout",
-        "reflect": false
+        "reflect": false,
+        "defaultValue": "5000"
       },
       "actionText": {
         "type": "string",

package/dist/collection/components/split-button/split-button.js

@@ -11,7 +11,6 @@ import { Host, h } from '@stencil/core';
  * The button should only be used for performing commands!
  * - Never use this component instead of a Select or Menu component!
  * :::
- *
  * @exampleComponent limel-example-split-button-basic
  * @exampleComponent limel-example-split-button-repeat-default-command
  */

package/dist/collection/components/tab-bar/tab-bar.js

@@ -14,14 +14,13 @@ const HIDE_SCROLL_BUTTONS_WHEN_SCROLLED_LESS_THAN_PX = 40;
  * :::
  * An exception for using tab bars in a high level of hierarchy is their usage in modals. This is because modals are perceived as a separate place and not a part of the current context. Therefore you can use tab bars in a modal to group and organize its content.
  * A tab bar can contain an unlimited number of tabs. However, depending on the device width and width of the tabs, the number of tabs that are visible at the same time will vary. When there is limited horizontal space, the component shows a left-arrow and/or right-arrow button, which scrolls and reveals the additional tabs. The tab bar can also be swiped left and right on a touch-device.
- *:::tip Other things to consider
+ * :::tip Other things to consider
  * Never divide the content of a tab using a nested tab bar.
  * Never place two tab bars within the same screen.
  * Never use background color for icons in tabs.
  * Avoid having long labels for tabs.
  * A tab will never be removed or get disabled, even if there is no content under it.
  * :::
- *
  * @exampleComponent limel-example-tab-bar
  * @exampleComponent limel-example-tab-bar-with-dynamic-tab-width
  * @exampleComponent limel-example-tab-bar-with-equal-tab-width

package/dist/collection/components/tab-bar/tabs.js

@@ -1,7 +1,6 @@
 /**
  * Set a tabs `active` state to true in a list of tabs. The previous tab with
  * `active` set to true will have it set to `false` instead.
- *
  * @param {Tab[]} tabs list of tabs
  * @param {number} index the index of the tab to set to active
  * @returns {Tab[]} a copy of the list of tabs with the changed tabs replaced

package/dist/collection/components/tab-panel/tab-panel.js

@@ -14,7 +14,6 @@ import { dispatchResizeEvent } from '../../util/dispatch-resize-event';
  *
  * The slotted components can also emit the `changeTab` event to update anything
  * inside the actual tab, e.g. to change the icon, color or badge.
- *
  * @slot - Content to put inside the `limel-tab-panel`. Each slotted element
  * must have the `id` attribute equal to the id of the tab it belongs to.
  * @exampleComponent limel-example-tab-panel