@lion/ui 0.21.1 → 0.22.0

package/vscode.html-custom-data.json

@@ -0,0 +1,789 @@
+{
+  "version": 1.1,
+  "tags": [
+    {
+      "name": "lion-accordion",
+      "description": "\n\n\n---\n\n\n\n\n### **Slots:**\n - **invoker** - The invoker element for the accordion\n- **content** - The content element for the accordion\n- **_accordion** - The slot for the accordion, used to rearrange invokers and content",
+      "attributes": [
+        {
+          "name": "focusedIndex",
+          "description": "index number of the focused accordion",
+          "values": []
+        },
+        {
+          "name": "expanded",
+          "description": "array of indices of the expanded accordions",
+          "values": [{ "name": "array" }]
+        },
+        {
+          "name": "exclusive",
+          "description": "exclusive property allows only one accordion slot to be open at a time",
+          "values": []
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-button",
+      "description": "Use LionButton (or LionButtonReset|LionButtonSubmit) when there is a need to extend HTMLButtonElement.\nIt allows to create complex shadow DOM for buttons needing this. Think of:\n- a material Design button that needs a JS controlled ripple\n- a LionSelectRich invoker that needs a complex shadow DOM structure\n(for styling/maintainability purposes)\n- a specialized button (for instance a primary button or icon button in a Design System) that\nneeds a simple api: `<my-button>text</my-button>` is always better than\n`<button class=\"my-button\"><div class=\"my-button__container\">text</div><button>`\n\nIn other cases, whenever you can, still use native HTMLButtonElement (`<button>`).\n\nNote that LionButton is meant for buttons with type=\"button\". It's cleaner and more\nlightweight than LionButtonReset and LionButtonSubmit, which should only be considered when native\n`<form>` support is needed:\n- When type=\"reset|submit\" should be supported, use LionButtonReset.\n- When implicit form submission should be supported on top, use LionButtonSubmit.\n\n\n---\n\n\n",
+      "attributes": [
+        { "name": "active", "values": [] },
+        { "name": "type", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-button-reset",
+      "description": "This adds functionality for form buttons (type 'submit' and 'reset').\nIt allows to submit or reset a <form> by spawning a click on a temporrary native button inside\nthe form.\nUse LionButtonSubmit when implicit form submission should be supported as well.\n\nFunctionality in this button is not purely for type=\"reset\", also for type=\"submit\".\nFor mainainability purposes the submit functionality is part of LionButtonReset\n(it needs the same logic).\nLionButtonReset could therefore actually be considered as 'LionButtonForm' (without the\nimplicit form submission logic), but LionButtonReset is an easier to grasp name for\nApplication Developers: for reset buttons, always use LionButtonReset, for submit\nbuttons always use LionButtonSubmit.\n\n\n---\n\n\n",
+      "attributes": [
+        { "name": "active", "values": [] },
+        { "name": "type", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-button-submit",
+      "description": "Contains all the funcionaility of LionButton and LionButtonReset. On top of that it\nsupports implicit form submission.\n\nUse when:\n- the Application Developer should be able to switch types between 'submit'|'reset'|'button'\n(this is similar to how native HTMLButtonElement works)\n- a submit button with native form support is needed\n\n\n---\n\n\n",
+      "attributes": [
+        { "name": "active", "values": [] },
+        { "name": "type", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-calendar",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-selected-date-changed** - undefined\n\n### **Methods:**\n - **initCentralDate()** - This exposes an interface for datepickers that want to\nreinitialize when calendar is opened",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-checkbox-group",
+      "description": "A wrapper around multiple checkboxes\n\n\n---\n\n\n",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-checkbox-indeterminate",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "indeterminate",
+          "description": "Indeterminate state of the checkbox",
+          "values": []
+        },
+        { "name": "mixed-state", "values": [] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-checkbox",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-collapsible",
+      "description": "`LionCollapsible` is a class for custom collapsible element (`<lion-collapsible>` web component).\n\n\n---\n\n\n\n\n### **Events:**\n - **opened-changed** - undefined\n\n### **Methods:**\n - **hide()** - Hide extra content.\n- **show()** - Show extra content.\n- **toggle()** - Toggle the current(opened/closed) state.\n- **_hideAnimation(opts: _Object_)** - Hide animation implementation in sub-classer.\n- **_showAnimation(opts: _Object_)** - Show animation implementation in sub-classer.\n\n### **Slots:**\n - **invoker** - The invoker element for the collapsible\n- **content** - The content element for the collapsible",
+      "attributes": [{ "name": "opened", "values": [] }],
+      "references": []
+    },
+    {
+      "name": "lion-combobox",
+      "description": "LionCombobox: implements the wai-aria combobox design pattern and integrates it as a Lion\nFormControl\n\n\n---\n\n\n\n\n### **Events:**\n - **model-value-changed** - undefined\n\n### **Methods:**\n - **matchCondition(option: _LionOption_, textboxValue: _string_)** - When the preconfigurable `match-mode` conditions are not sufficient,\none can define a custom matching function.\n- **parser(value: _string|string[]_): _*_** - Converts viewValue to modelValue\n- **_autoSelectCondition()** - When this condition is false, an end user will have to manually select a suggested\noption from the list (by default when autocomplete is 'none' or 'list').\nFor autocomplete 'both' or 'inline', it will automatically select on a match.\n- **_getTextboxValueFromOption(option: _LionOption_): _string_** - Return the value to be used for the input value\n- **_handleAutocompletion()** - Handles autocompletion. This entails:\n- list: shows a list on keydown character press\n- filter: filters list of potential matches according to matchmode or provided matchCondition\n- focus: automatically focuses closest match (makes it the activedescendant)\n- check: automatically checks/selects closest match when selection-follows-focus is enabled\n(this is the default configuration)\n- complete: completes the textbox value inline (the 'missing characters' will be added as\nselected text)\n\n### **Slots:**\n - **listbox** - The listbox element for the combobox, e.g. <lion-options>\n- **selection-display** - The selection display element for the combobox, e.g. <lion-selection-display>",
+      "attributes": [
+        {
+          "name": "autocomplete",
+          "description": "When \"list\", will filter listbox suggestions based on textbox value.\nWhen \"both\", an inline completion string will be added to the textbox as well.",
+          "values": [
+            { "name": "none" },
+            { "name": "list" },
+            { "name": "inline" },
+            { "name": "both" }
+          ]
+        },
+        {
+          "name": "match-mode",
+          "description": "When typing in the textbox, will by default be set on 'begin',\nonly matching the beginning part in suggestion list.\n=> 'a' will match 'apple' from ['apple', 'pear', 'citrus'].\nWhen set to 'all', will match middle of the word as well\n=> 'a' will match 'apple' and 'pear'",
+          "values": [{ "name": "begin" }, { "name": "all" }]
+        },
+        {
+          "name": "show-all-on-empty",
+          "description": "When true, the listbox is open and textbox goes from a value to empty, all options are shown.\nBy default, the listbox closes on empty, similar to wai-aria example and <datalist>",
+          "values": []
+        },
+        {
+          "name": "requireOptionMatch",
+          "description": "If set to false, the value is allowed to not match any of the options.\nWe set the default to true for backwards compatibility",
+          "values": []
+        },
+        { "name": "allow-custom-choice", "values": [] },
+        { "name": "__shouldAutocompleteNextUpdate", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-dialog",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [{ "name": "is-alert-dialog", "values": [] }],
+      "references": []
+    },
+    {
+      "name": "lion-drawer",
+      "description": "LionDrawer: extension of lion-collapsible with drawer specific styles and animations\n\n\n---\n\n\n\n\n### **Events:**\n - **opened-changed** - undefined\n\n### **Methods:**\n - **hide()** - Hide extra content.\n- **show()** - Show extra content.\n- **toggle()** - Toggle the current(opened/closed) state.\n- **_hideAnimation({ contentNode }, options: _@param {HTMLElement} options.contentNode\n   * _)** - Trigger hide animation and wait for transition to be finished.\n- **_showAnimation({ contentNode }, options: _@param {HTMLElement} options.contentNode\n   * _)** - Trigger show animation and wait for transition to be finished.\n- **_waitForTransition({ contentNode }, options: _@param {HTMLElement} options.contentNode\n   * _): _Promise<void>_** - Wait until the transition event is finished.\n\n### **Slots:**\n - **invoker** - The invoker element for the drawer\n- **content** - The content element for the drawer\n- **headline** - The headline element for the drawer",
+      "attributes": [
+        { "name": "transitioning", "values": [] },
+        { "name": "opened", "values": [] },
+        {
+          "name": "position",
+          "description": "Setter for position property, available values are 'top', 'left' and 'right'",
+          "values": []
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-fieldset",
+      "description": "LionFieldset is basically a 'sub form' and can have its own nested sub forms.\nIt mimics the native <fieldset> element in this sense, but has all the functionality of\na FormControl (advanced styling, validation, interaction states etc.) Also see\nFormGroupMixin it depends on.\n\nLionFieldset enables the '_isFormOrFieldset' flag in FormRegistrarMixin. This makes .formElements\nact not only as an array, but also as an object (see FormRegistarMixin for more information).\nAs a bonus, It can also group children having names ending with '[]'.\n\nAbove will be  helpful for both forms and sub forms, which can contain sub forms as children\nas well and allow for a nested form structure.\nContrary, other form groups (choice groups like radio-group, checkbox-group and (multi)select)\ndon't: they should be considered 'end nodes' or 'leaves' of the form and their children/formElements\ncannot be accessed individually via object keys.\n\n\n---\n\n\n",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "choice-input-foo",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "choice-input-bar",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "choice-input",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "choice-input-group",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "choice-input",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "tagString",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-field",
+      "description": "`LionField`: wraps <input>, <textarea>, <select> and other interactable elements.\nAlso it would follow a nice hierarchy: lion-form -> lion-fieldset -> lion-field\n\nNote: We don't support placeholders, because we have a helper text and\nplaceholders confuse the user with accessibility needs.\n\nPlease see the docs for in depth information.\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-validation-feedback",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-form",
+      "description": "LionForm: form wrapper providing extra features and integration with lion-field elements.\n\n\n---\n\n\n\n\n### **Events:**\n - **submit** - undefined\n- **reset** - undefined",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "sb-action-logger",
+      "description": "\n\n\n---\n\n\n\n\n### **Methods:**\n - **log(content: _string_)** - Renders the passed content as a node, and appends it to the logger\nOnly supports simple values, will be interpreted to a String\nE.g. an Object will become '[object Object]'\n- **_logTemplate(content: _string_): _TemplateResult_** - Protected getter that returns the template of a single log",
+      "attributes": [
+        { "name": "title", "values": [] },
+        { "name": "simple", "values": [] },
+        { "name": "__logCounter", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "sb-locale-switcher",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [
+        { "name": "show-locales", "values": [{ "name": "array" }] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-icon",
+      "description": "Custom element for rendering SVG icons\n\n\n---\n\n\n",
+      "attributes": [
+        { "name": "aria-label", "values": [] },
+        { "name": "icon-id", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-amount-dropdown",
+      "description": "LionInputAmountDropdown renders a dropdown like element next to the text field, inside the\nprefix, or suffix, slot. This could be a LionSelect, a LionSelectRich or a native select.\nBy default, the native `<select>` element is used for this, so that it's as lightweight as\npossible. Also, it doesn't need to be a `FormControl`, because it's purely a helper element\nto provide better UX: the modelValue (the text field) contains all needed info:\nthe currency code following ISO 4217 and its corresponding currency symbol using Intl.\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_connectSlotMixin()** - Upon connecting slot mixin, we should check if\nthe required slot was created by the slot mixin,\nand if so, we should execute the currency changed flow\nwhich evaluates whether the slot node should be\nremoved for invalid currencies\n- **_isEmpty(modelValue): _boolean_** - Used for Required validation and computation of interaction states.\nWe only consider the amount part for emptiness checks.\nMissing, null, empty-string or NaN amount is considered empty.\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_repropagationCondition()** - Usually, we don't use composition in regular LionFields (non choice-groups). Here we use a LionSelect(Rich) inside.\nWe don't want to repropagate any children, since an Application Developer is not concerned with these internals (see repropate logic in FormControlMixin)\nAlso, we don't want to give (wrong) info to InteractionStateMixin, that will set the wrong interaction states based on child info.\nTODO: Make \"this._repropagationRole !== 'child'\" the default for FormControlMixin\n(so that FormControls used within are never repropagated for LionFields)",
+      "attributes": [
+        {
+          "name": "preferredCurrencies",
+          "description": "Regions that will be shown on top of the dropdown",
+          "values": [{ "name": "CurrencyCode[]" }]
+        },
+        {
+          "name": "allowedCurrencies",
+          "description": "Regions that are allowed to be selected in the dropdown.",
+          "values": [{ "name": "CurrencyCode[]" }]
+        },
+        {
+          "name": "__dropdownSlot",
+          "description": "Slot position to render the dropdown in",
+          "values": []
+        },
+        { "name": "currency", "values": [] },
+        { "name": "modelValue", "values": [] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": [null]
+    },
+    {
+      "name": "lion-input-amount",
+      "description": "`LionInputAmount` is a class for an amount custom form element (`<lion-input-amount>`).\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_connectSlotMixin()** - Upon connecting slot mixin, we should check if\nthe required slot was created by the slot mixin,\nand if so, we should execute the currency changed flow\nwhich evaluates whether the slot node should be\nremoved for invalid currencies\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        { "name": "currency", "values": [] },
+        { "name": "modelValue", "values": [] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-date",
+      "description": "`LionInputDate` has a .modelValue of type Date. It parses, formats and validates based\non locale.\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        { "name": "modelValue", "values": [] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-datepicker",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_calendarTemplate()** - Subclassers can replace this with their custom extension of\nLionCalendar, like `<my-calendar id=\"calendar\"></my-calendar>`\n- **_invokerIconTemplate()** - Subclassers can replace this with their custom extension invoker icon\n- **_invokerTemplate()** - Subclassers can replace this with their custom extension invoker,\nlike `<my-button><calendar-icon></calendar-icon></my-button>`\n- **_onCalendarOverlayOpened()** - Lifecycle callback for subclassers\n- **_onCalendarUserSelectedChanged({ target: { selectedDate } }, opts: _{ target: { selectedDate: Date }}_)** - Triggered when a user selects a date from the calendar overlay\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_onValidatorUpdated(e: _Event|CustomEvent_, metaData: _{validator: Validator}_)** - Responsible for listening param change event and\nsync the calendar dates with the updated validator params\n- **_overlayTemplate()** - Defining this overlay as a templates from OverlayMixin\nthis is our source to give as .contentNode to OverlayController.\nImportant: do not change the name of this method.",
+      "attributes": [
+        {
+          "name": "calendar-heading",
+          "description": "The heading to be added on top of the calendar overlay.\nNaming chosen from an Application Developer perspective.\nFor a Subclasser 'calendarOverlayHeading' would be more appropriate.",
+          "values": []
+        },
+        { "name": "modelValue", "values": [] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-email",
+      "description": "LionInputEmail: extension of lion-input\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-file",
+      "description": "LionInputFile: A file input component\nThis component allows users to select files, displays selected files, and handles file uploads.\n\n\n---\n\n\n\n\n### **Events:**\n - **file-list-changed** - undefined\n- **file-removed** - undefined\n- **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_isEmpty()** - Helper method for the mutually exclusive Required Validator\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_onClick(ev: _Event_)** - Clear _inputNode.value to make sure onChange is called even for duplicate files\n- **_processFiles(selectedFiles: _InputFile[]_)** - Runs on drag or change event\n- **_reflectBackOn(): _boolean_** - Every time .formattedValue is attempted to sync to the view value (on change/blur and on\nmodelValue change), this condition is checked. In case of the input-file we don't want\nthis sync to happen, since the view value is already correct.\n- **_updateUploadButtonDescription()** - Description for screen readers connected to the button about how many files have been updated\n\n### **Slots:**\n - **file-select-button** - [private] The button to open the file dialog\n- **selected-file-list** - [private] The list of selected files",
+      "attributes": [
+        { "name": "accept", "values": [] },
+        { "name": "multiple", "values": [] },
+        {
+          "name": "button-label",
+          "description": "The label of the button",
+          "values": []
+        },
+        { "name": "max-file-size", "values": [] },
+        { "name": "enable-drop-zone", "values": [] },
+        { "name": "upload-on-select", "values": [] },
+        { "name": "is-dragging", "values": [] },
+        {
+          "name": "uploadResponse",
+          "values": [{ "name": "UploadResponse[]" }]
+        },
+        {
+          "name": "_selectedFilesMetaData",
+          "values": [{ "name": "InputFile[]" }]
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-selected-file-list",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **file-remove-requested** - undefined",
+      "attributes": [
+        { "name": "fileList", "values": [{ "name": "InputFile[]" }] },
+        { "name": "multiple", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-iban",
+      "description": "`LionInputIban` is a class for an IBAN custom form element (`<lion-input-iban>`).\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "`lion-input-range`",
+      "description": "LionInputRange: extension of lion-input.\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        { "name": "min", "values": [] },
+        { "name": "max", "values": [] },
+        { "name": "unit", "values": [] },
+        { "name": "step", "values": [] },
+        { "name": "no-min-max-labels", "values": [] },
+        { "name": "min-label", "values": [] },
+        { "name": "max-label", "values": [] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-stepper",
+      "description": "`LionInputStepper` is a class for custom input-stepper element (`<lion-input-stepper>` web component).\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_decrement(ev: _Event_)** - Decrement the value based on given step or default step value is 1\n- **_decrementorSignTemplate(): _String|TemplateResult_** - Get the decrementor button sign template\n- **_decrementorTemplate(): _TemplateResult_** - Get the increment button template\n- **_increment(ev: _Event_)** - Increment the value based on given step or default step value is 1\n- **_incrementorSignTemplate(): _String|TemplateResult_** - Get the incrementor button sign template\n- **_incrementorTemplate(): _TemplateResult_** - Get the decrement button template\n- **_onChange(ev: _Event=_)** - Toggle +/- buttons on change",
+      "attributes": [
+        { "name": "min", "values": [] },
+        { "name": "max", "values": [] },
+        {
+          "name": "valueTextMapping",
+          "description": "The aria-valuetext attribute defines the human-readable text alternative of aria-valuenow.",
+          "values": [{ "name": "{[key: number]: string}" }]
+        },
+        { "name": "step", "values": [] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input-tel-dropdown",
+      "description": "LionInputTelDropdown renders a dropdown like element next to the text field, inside the\nprefix slot. This could be a LionSelect, a LionSelectRich or a native select.\nBy default, the native `<select>` element is used for this, so that it's as lightweight as\npossible. Also, it doesn't need to be a `FormControl`, because it's purely a helper element\nto provide better UX: the modelValue (the text field) contains all needed info, since it's in\n`e164` format that contains all info (both region code and national phone number).\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_isEmpty(modelValue: _string_): _boolean_** - Used for Required validation and computation of interaction states.\nWe need to override this, because we prefill the input with the region code (like +31), but for proper UX,\nwe don't consider this as having interaction state `prefilled`\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_reflectBackOn(): _boolean_** - Do not reflect back .formattedValue during typing (this normally wouldn't happen when\nFormatMixin calls _calculateValues based on user input, but for LionInputTel we need to\ncall it on .activeRegion change)\n- **_repropagationCondition()** - Usually, we don't use composition in regular LionFields (non choice-groups). Here we use a LionSelect(Rich) inside.\nWe don't want to repropagate any children, since an Application Developer is not concerned with these internals (see repropate logic in FormControlMixin)\nAlso, we don't want to give (wrong) info to InteractionStateMixin, that will set the wrong interaction states based on child info.\nTODO: Make \"this._repropagationRole !== 'child'\" the default for FormControlMixin\n(so that FormControls used within are never repropagated for LionFields)\n- **_setActiveRegion(newValue: _RegionCode|undefined_)** - Protected setter for activeRegion, only meant for subclassers",
+      "attributes": [
+        {
+          "name": "allowedRegions",
+          "description": "The regions that should be considered when international phone numbers are detected.\n(when not configured, all regions worldwide will be considered)",
+          "values": [{ "name": "RegionCode[]" }]
+        },
+        {
+          "name": "format-strategy",
+          "description": "Determines what the formatter output should look like.\nFormatting strategies as provided by google-libphonenumber\nSee: https://www.npmjs.com/package/google-libphonenumber",
+          "values": [{ "name": "PhoneNumberFormat" }]
+        },
+        {
+          "name": "format-country-code-style",
+          "description": "Extra styling of the format strategy\ndefault | parentheses",
+          "values": []
+        },
+        {
+          "name": "activeRegion",
+          "description": "Currently active region based on:\n1. allowed regions: get the region from configured allowed regions (if one entry)\n2. user input: try to derive active region from user input\n3. locale: try to get the region from locale (`html[lang]` attribute)",
+          "values": []
+        },
+        {
+          "name": "preferredRegions",
+          "description": "Regions that will be shown on top of the dropdown",
+          "values": [{ "name": "RegionCode[]" }]
+        },
+        { "name": "_phoneUtil", "values": [{ "name": "AwesomePhoneNumber" }] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": [null]
+    },
+    {
+      "name": "lion-input-tel",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_reflectBackOn(): _boolean_** - Do not reflect back .formattedValue during typing (this normally wouldn't happen when\nFormatMixin calls _calculateValues based on user input, but for LionInputTel we need to\ncall it on .activeRegion change)\n- **_setActiveRegion(newValue: _RegionCode|undefined_)** - Protected setter for activeRegion, only meant for subclassers",
+      "attributes": [
+        {
+          "name": "allowedRegions",
+          "description": "The regions that should be considered when international phone numbers are detected.\n(when not configured, all regions worldwide will be considered)",
+          "values": [{ "name": "RegionCode[]" }]
+        },
+        {
+          "name": "format-strategy",
+          "description": "Determines what the formatter output should look like.\nFormatting strategies as provided by google-libphonenumber\nSee: https://www.npmjs.com/package/google-libphonenumber",
+          "values": [{ "name": "PhoneNumberFormat" }]
+        },
+        {
+          "name": "format-country-code-style",
+          "description": "Extra styling of the format strategy\ndefault | parentheses",
+          "values": []
+        },
+        {
+          "name": "activeRegion",
+          "description": "Currently active region based on:\n1. allowed regions: get the region from configured allowed regions (if one entry)\n2. user input: try to derive active region from user input\n3. locale: try to get the region from locale (`html[lang]` attribute)",
+          "values": []
+        },
+        {
+          "name": "preferredRegions",
+          "description": "Regions that will be shown on top of the dropdown",
+          "values": [{ "name": "RegionCode[]" }]
+        },
+        { "name": "_phoneUtil", "values": [{ "name": "AwesomePhoneNumber" }] },
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-input",
+      "description": "LionInput: extension of lion-field with native input element in place and user friendly API.\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-listbox",
+      "description": "LionListbox: implements the wai-aria listbox design pattern and integrates it as a Lion\nFormControl\n\n\n---\n\n\n",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-option",
+      "description": "https://developer.mozilla.org/en-US/docs/Web/HTML/Element/option\nCan be a child of datalist/select, or role=\"listbox\"\n\nElement gets state supplied externally, reflects this to attributes,\nenabling SubClassers to style based on those states\n\n\n---\n\n\n\n\n### **Events:**\n - **active-changed** - undefined",
+      "attributes": [{ "name": "active", "values": [] }],
+      "references": [null]
+    },
+    {
+      "name": "lion-options",
+      "description": "LionOptions\n\n\n---\n\n\n",
+      "attributes": [{ "name": "tabindex", "values": [] }],
+      "references": [null]
+    },
+    {
+      "name": "lion-pagination",
+      "description": "`LionPagination` is a class for custom Pagination element (`<lion-pagination>` web component).\n\n\n---\n\n\n\n\n### **Methods:**\n - **first()** - Go to first page\n- **goto(pageNumber: _number_)** - Go to the specific page\n- **last()** - Go to the last page\n- **next()** - Go next in pagination\n- **previous()** - Go back in pagination\n- **_disabledButtonTemplate(label: _String_): _TemplateResult_** - Get disabled button template.\nThis method can be overridden to apply customized template in wrapper.\n- **_prevNextButtonTemplate(label: _String_, pageNumber: _Number_, namespace: _String_): _TemplateResult_** - Get next or previous button template.\nThis method can be overridden to apply customized template in wrapper.\n- **_prevNextIconTemplate(label: _String_): _TemplateResult_** - Get previous or next button template.\nThis method can be overridden to apply customized template in wrapper.\n- **_renderNavList(): _TemplateResult[]_** - Render navigation list",
+      "attributes": [
+        { "name": "current", "values": [] },
+        { "name": "count", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-progress-indicator",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [
+        { "name": "value", "values": [] },
+        { "name": "min", "values": [] },
+        { "name": "max", "values": [] },
+        { "name": "aria-label", "values": [] },
+        { "name": "aria-labelledby", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-radio-group",
+      "description": "LionRadioGroup: A wrapper around multiple radios.\n\n\n---\n\n\n",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-radio",
+      "description": "Lion-radio can be used inside a lion-radio-group.\n\n<lion-radio-group name=\"radios\">\n  <label slot=\"label\">My Radio</label>\n  <lion-radio>\n    <label slot=\"label\">Male</label>\n  </lion-radio>\n  <lion-radio>\n    <label slot=\"label\">Female</label>\n  </lion-radio>\n</lion-radio-group>\n\nYou can preselect an option by setting marking an lion-radio checked.\n  Example:\n  <lion-radio checked>\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "readonly",
+          "description": "A Boolean attribute which, if present, indicates that the user should not be able to edit\nthe value of the input. The difference between disabled and readonly is that read-only\ncontrols can still function, whereas disabled controls generally do not function as\ncontrols until they are enabled.\n\n(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly)",
+          "values": []
+        },
+        { "name": "type", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-field-with-select",
+      "description": "LionSelectRich: wraps the <lion-listbox> element\n\n\n---\n\n\n\n\n### **Events:**\n - **blur** - undefined\n\n### **Methods:**\n - **_alignInvokerWidth()** - Align invoker width with content width\nMake sure display is not set to \"none\" while calculating the content width\n- **_getCheckedElements()** - In the select disabled options are still going to a possible value for example\nwhen prefilling or programmatically setting it.\n- **_noDefaultSelectedInheritsWidth()** - With no selected element, we should override the inheritsReferenceWidth in most cases.\nBy default, we will set it to 'min', and then set it back to what it was initially when\nsomething is selected.\nAs a subclasser you can override this behavior.",
+      "attributes": [
+        {
+          "name": "navigate-within-invoker",
+          "description": "When invoker has focus, up and down arrow keys changes active state of listbox,\nwithout opening overlay.",
+          "values": [{ "name": "Boolean" }]
+        },
+        {
+          "name": "interaction-mode",
+          "description": "Aligns behavior for 'selectionFollowFocus' and 'navigateWithinInvoker' with\nplatform. When 'auto' (default), platform is automatically detected",
+          "values": [
+            { "name": "windows/linux" },
+            { "name": "mac" },
+            { "name": "auto" }
+          ]
+        },
+        { "name": "single-option", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-select-invoker",
+      "description": "LionSelectInvoker: invoker button consuming a selected element\n\n\n---\n\n\n\n\n### **Methods:**\n - **_noSelectionTemplate(): _TemplateResult_** - To be overriden for a placeholder, used when `hasNoDefaultSelected` is true on the select rich",
+      "attributes": [
+        {
+          "name": "selectedElement",
+          "description": "The option element that is currently selected",
+          "values": [{ "name": "LionOption" }]
+        },
+        {
+          "name": "hostElement",
+          "description": "The LionSelectRich element this invoker is part of. Will be set on connectedCallback of\nLionSelectRich",
+          "values": [{ "name": "LionSelectRich" }]
+        },
+        {
+          "name": "readonly",
+          "description": "When the connected LionSelectRich instance is readOnly,\nthis should be reflected in the invoker as well",
+          "values": []
+        },
+        {
+          "name": "single-option",
+          "description": "When the connected LionSelectRich instance has only one option,\nthis should be reflected in the invoker as well",
+          "values": []
+        },
+        { "name": "active", "values": [] },
+        { "name": "type", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-select",
+      "description": "LionSelect: wraps the native HTML element select\n\n<lion-select>\n  <label slot=\"label\">My Input</label>\n  <select slot=\"input\">\n   <option value=\"top\">top</option>\n   <option value=\"bottom\">bottom</option>\n  </select>\n</lion-select>\n\nYou can preselect an option by setting the property modelValue.\n  Example:\n    <lion-select .modelValue=\"${'<value of option 2>'}\">\n\nIt extends LionField so it inherits required and disabled.\n\nThe option element needs to be a direct child of the select element.\n\nYou cannot use interactive elements inside the options. Avoid very long names to\nfacilitate the understandability and perceivability for screen reader users. Sets of options\nwhere each option name starts with the same word or phrase can also significantly degrade\nusability for keyboard and screen reader users.\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        {
+          "name": "autocomplete",
+          "description": "Delegates autocomplete to select",
+          "values": []
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-steps",
+      "description": "`LionSteps` is a controller for a multi step system.\n\n\n---\n\n\n\n\n### **Events:**\n - **transition** - undefined",
+      "attributes": [
+        {
+          "name": "data",
+          "description": "Storage for data gathered across different steps.\nData is passed into each step condition function as a first argument.",
+          "values": [{ "name": "{[key: string]: any}" }]
+        },
+        {
+          "name": "current",
+          "description": "Number of the current entered step.",
+          "values": []
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-step",
+      "description": "`LionStep` is one of many in a LionSteps Controller\n\n\n---\n\n\n\n\n### **Events:**\n - **enter** - undefined\n- **leave** - undefined\n- **skip** - undefined",
+      "attributes": [
+        {
+          "name": "status",
+          "description": "Step status, one of: \"untouched\", \"entered\", \"left\", \"skipped\".",
+          "values": []
+        },
+        {
+          "name": "invert-condition",
+          "description": "Allows to invert condition function result.",
+          "values": []
+        },
+        {
+          "name": "forward-only",
+          "description": "Allows transition to step only in forward direction. Skips it if transitioned back.\nMay be useful if the step is only showing some messages and does data loading and\nthen makes transition to next step automatically.",
+          "values": []
+        },
+        {
+          "name": "initial-step",
+          "description": "If set this step will be the initially enabled step\nThere should be only ONE intial step in each steps",
+          "values": []
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-switch",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_isEmpty()** - Override this function from ChoiceInputMixin.\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_toggleChecked(ev: _Event_)** - Override this function from ChoiceInputMixin.",
+      "attributes": [],
+      "references": []
+    },
+    {
+      "name": "lion-switch-button",
+      "description": "`LionSwitchButton` is a custom switch button component. It's a private component used within LionSwitch\n\n\n---\n\n\n\n\n### **Events:**\n - **checked-changed** - undefined",
+      "attributes": [
+        { "name": "checked", "values": [] },
+        { "name": "readonly", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-tabs",
+      "description": "LionTabs: A tabbed interface component\n\n\n---\n\n\n\n\n### **Events:**\n - **selected-changed** - undefined\n\n### **Slots:**\n - **tab** - The tab elements for the tabs\n- **panel** - The panel elements for the tabs",
+      "attributes": [
+        {
+          "name": "selected-index",
+          "description": "An index number of the selected tab",
+          "values": []
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-textarea",
+      "description": "LionTextarea: extension of lion-field with native input element in place and user friendly API\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **setTextareaMaxHeight()** - To support maxRows we need to set max-height of the textarea\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
+      "attributes": [
+        { "name": "max-rows", "values": [] },
+        { "name": "rows", "values": [] },
+        { "name": "readonly", "values": [] },
+        { "name": "placeholder", "values": [] }
+      ],
+      "references": []
+    },
+    {
+      "name": "lion-tooltip",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [
+        {
+          "name": "invoker-relation",
+          "description": "Decides whether the tooltip invoker text should be considered a description\n(sets aria-describedby) or a label (sets aria-labelledby).",
+          "values": [{ "name": "label" }, { "name": "description" }]
+        }
+      ],
+      "references": []
+    },
+    {
+      "name": "wrapperTagName",
+      "description": "\n\n\n---\n\n\n\n\n### **Methods:**\n - **defineScopedElement(tagName: _string_, classToBeRegistered: _typeof HTMLElement_)** - Defines a scoped element.",
+      "attributes": [
+        {
+          "name": "scopedElements",
+          "values": [{ "name": "ScopedElementsMap" }]
+        },
+        { "name": "template", "values": [{ "name": "LitHTMLRenderable" }] }
+      ],
+      "references": []
+    }
+  ]
+}