@lion/ui 0.21.1-menu-system.0 → 0.22.0

package/docs/guides/how-to/create-a-custom-field.md

@@ -87,9 +87,9 @@ if (!customElements.get('dummy-slider')) {
 }
 ```
 
-Custom Fields can be created in just a few steps. All you need is an interaction element (like for instance a slider, a listbox or a combobox) and connect it to the [LionField](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/components/input/overview.md).
+Custom Fields can be created in just a few steps. All you need is an interaction element (like for instance a slider, a listbox or a combobox) and connect it to the [LionField](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components/input/overview.md).
 
-> In case you want to extend a native element, follow [Extend a native Input](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/extend-a-native-input.md).
+> In case you want to extend a native element, follow [Extend a native Input](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/extend-a-native-input.md).
 
 ## A) an interaction element
 
@@ -138,7 +138,7 @@ export const createAnInteractiveElement = () => {
 ## B) your LionField extension
 
 Now we want to integrate the slider in our form system to enrich the user interface, get
-validation support and all other [benefits of LionField](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/components/input/overview.md).
+validation support and all other [benefits of LionField](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components/input/overview.md).
 We start by creating a component `<slider-field>` that extends from `LionField`.
 Then we follow the steps below:
 
@@ -151,7 +151,7 @@ Then we follow the steps below:
 
   The `user-input-changed` event is listened to by the FormatMixin: it should be regarded as the
   equivalent of the `input` event of the platform, but for custom built interaction elements.
-  You now synchronized [modelValue](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/fundamentals/systems/form/model-value.md), which can be regarded as
+  You now synchronized [modelValue](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/fundamentals/systems/form/model-value.md), which can be regarded as
   the glue to integrate all other functionality like parsing/formatting/serializing, validating,
   tracking interaction states etc.
 
@@ -159,7 +159,7 @@ Then we follow the steps below:
 > because those properties will lose their reactivity (they won't be considered anymore in the
 > update loop of LitElement).
 > Whenever a .modelValue/.formattedValue/.serializedValue needs to be computed, use
-> [parser/formatter/serializer](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/fundamentals/systems/form/formatting-and-parsing.md)
+> [parser/formatter/serializer](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/fundamentals/systems/form/formatting-and-parsing.md)
 
 Implement with the following code:
 

package/docs/guides/how-to/create-a-form.md

@@ -39,7 +39,7 @@ Large or complex forms might need to be split up into multiple files. This compo
 
 In the latter case: make sure that your components don't have a shadow root. This can be achieved by rendering into Light DOM. The form registration mechanism relies on light dom by design: as soon as you do start to use shadow roots, you will notice that your form components won't register themselves anymore to their parents.
 
-> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
+> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
 
 ### Example of a component that renders into Light DOM
 
@@ -86,7 +86,7 @@ Extending form components is not recommended for Application Developers: it shou
 This team will add the styling and default configuration needed to make it fit the particular Design System.
 
 With the toolbox provided by the team that creates your Design System, you should be able to build all your forms. Only if you have a really good reason, look into
-[exceptional cases](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/#exceptional-cases) below.
+[exceptional cases](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/#exceptional-cases) below.
 
 ### Exceptional cases
 
@@ -94,8 +94,8 @@ If the form component you need is still missing, you have two options:
 
 - is it a generic primitive that should be part of Lion? Request it in [Lion discussions](https://github.com/ing-bank/lion/discussions)
 - is it a non generic component that is unique to your app?
-  - follow [create a custom field](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/create-a-custom-field.md)
-  - follow [extend a native input](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/extend-a-native-input.md)
+  - follow [create a custom field](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/create-a-custom-field.md)
+  - follow [extend a native input](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/extend-a-native-input.md)
 
 It's also possible to extend other components, like LionListbox or LionCombobox. You need to be aware that you're building on top of protected apis.
 Changing/overriding functionality is only recommended if the source code in `form-core` is fully understood.

package/docs/guides/how-to/extend-a-native-input.md

@@ -23,9 +23,9 @@ import '../../fundamentals/systems/form/assets/h-output.js';
 loadDefaultFeedbackMessages();
 ```
 
-Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/components/input/overview.md).
+Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components/input/overview.md).
 
-> In case you want to wrap a custom form element, follow [Create a custom Field](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/create-a-custom-field.md).
+> In case you want to wrap a custom form element, follow [Create a custom Field](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/create-a-custom-field.md).
 
 For this tutorial, we create an input that wraps native `input[type=datetime-local]`.
 This is as simple as adding a type:

package/docs/guides/how-to/index.md

@@ -22,4 +22,4 @@ Whether you're just getting started with Lion, building your first form, extendi
 - Build custom form fields tailored to your needs
 - Follow proven patterns and best practices used by the Lion community
 
-If you can't find what you're looking for, check out our [Fundamentals](../../fundamentals/) section for deeper conceptual knowledge, or visit our [Components](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/components) documentation for detailed API references.
+If you can't find what you're looking for, check out our [Fundamentals](../../fundamentals/) section for deeper conceptual knowledge, or visit our [Components](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components) documentation for detailed API references.

package/docs/guides/index.md

@@ -22,9 +22,9 @@ Developers consuming our web components inside an application (not extending the
 `Application Developers` are only allowed to interact with `public` properties and methods.
 Can be abbreviated as `AD`. Sometimes also called `Consuming Developer`.
 
-- [Definitions and Terms](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -32,13 +32,13 @@ Developers extending our web components, for instance: `class MaterialInput exte
 
 Especially for subclassers we have some extra documentation:
 
-- [Subclasser APIs](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/blog/extending-documentation.md)
 
 ## How To
 
 Next to that we have some specific "How To" documentations.
 
-- [Get started](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/get-started.md)
-- [Create a custom field](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/create-a-custom-field.md)
-- [Extend a native input](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/how-to/extend-a-native-input.md)
+- [Get started](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/get-started.md)
+- [Create a custom field](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/create-a-custom-field.md)
+- [Extend a native input](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/extend-a-native-input.md)

package/docs/guides/principles/index.md

@@ -22,9 +22,9 @@ Developers consuming our web components inside an application (not extending the
 `Application Developers` are only allowed to interact with `public` properties and methods.
 Can be abbreviated as `AD`. Sometimes also called `Consuming Developer`.
 
-- [Definitions and Terms](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -32,5 +32,5 @@ Developers extending our web components, for instance: `class MaterialInput exte
 
 Especially for subclassers we have some extra documentation:
 
-- [Subclasser APIs](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/blog/extending-documentation.md)

package/docs/guides/principles/styling.md

@@ -30,7 +30,7 @@ Examples for both categories can be found below:
 - Accessibility examples:
   - Content (for instance a caption in a table) can be `visually hidden`: it will be
     readable by screen readers, but invisible for end users.
-  - When an html table is used, we allow [subclassers](https://github.com/ing-bank/lion/blob/7f56e68987f13e6c536ea8f5d771f222a9f94a17/docs/guides/principles/subclasser-apis.md) to override the display property (`table-cell`) to `flex`. By putting the proper accessible roles (`role="cell"`) in the markup, we guarantee our markup stays accessible.
+  - When an html table is used, we allow [subclassers](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/subclasser-apis.md) to override the display property (`table-cell`) to `flex`. By putting the proper accessible roles (`role="cell"`) in the markup, we guarantee our markup stays accessible.
 
 Although Lion components try to stay as unbiased as possible with regard to styling, defaults will be needed. In these cases we try to follow the platform as much as possible. If the platform doesn't provide defaults, the largest common denominator across existing UI systems is taken as a lead.
 

package/exports/overlays.js

@@ -9,8 +9,6 @@ export { withModalDialogConfig } from '../components/overlays/src/configurations
 export { withDropdownConfig } from '../components/overlays/src/configurations/withDropdownConfig.js';
 export { withTooltipConfig } from '../components/overlays/src/configurations/withTooltipConfig.js';
 export { withPopoverConfig } from '../components/overlays/src/configurations/withPopoverConfig.js';
-export { withClickInteraction } from '../components/overlays/src/configurations/visibility-trigger-partials/withClickInteraction.js';
-export { withHoverInteraction } from '../components/overlays/src/configurations/visibility-trigger-partials/withHoverInteraction.js';
 
 export { deepContains } from '../components/overlays/src/utils/deep-contains.js';
 // re-export via this entrypoint for backwards compatibility
@@ -22,7 +20,3 @@ export {
 } from '../components/overlays/src/utils/inert-siblings.js';
 
 export { overlays } from '../components/overlays/src/singleton.js';
-
-/**
- * @typedef {import('../components/overlays/types/OverlayConfig.js').OverlayConfig} OverlayConfig
- */

package/overlays.js

@@ -7,8 +7,6 @@ export { withModalDialogConfig } from './components/overlays/src/configurations/
 export { withDropdownConfig } from './components/overlays/src/configurations/withDropdownConfig.js';
 export { withTooltipConfig } from './components/overlays/src/configurations/withTooltipConfig.js';
 export { withPopoverConfig } from './components/overlays/src/configurations/withPopoverConfig.js';
-export { withClickInteraction } from './components/overlays/src/configurations/visibility-trigger-partials/withClickInteraction.js';
-export { withHoverInteraction } from './components/overlays/src/configurations/visibility-trigger-partials/withHoverInteraction.js';
 export { deepContains } from './components/overlays/src/utils/deep-contains.js';
 // re-export via this entrypoint for backwards compatibility
 export { getDeepActiveElement } from './components/core/src/getDeepActiveElement.js';
@@ -18,7 +16,3 @@ export {
   setSiblingsInert,
 } from './components/overlays/src/utils/inert-siblings.js';
 export { overlays } from './components/overlays/src/singleton.js';
-
-/**
- * @typedef {import('../components/overlays/types/OverlayConfig.js').OverlayConfig} OverlayConfig
- */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lion/ui",
-  "version": "0.21.1-menu-system.0",
+  "version": "0.22.0",
   "description": "A package of extendable web components",
   "license": "MIT",
   "author": "ing-bank",
@@ -81,6 +81,9 @@
     "dist-types",
     "docs",
     "exports",
+    "vscode.css-custom-data.json",
+    "vscode.html-custom-data.json",
+    "web-types.json",
     "!custom-elements-manifest.config.js"
   ],
   "scripts": {
@@ -124,9 +127,10 @@
     "access": "public"
   },
   "customElements": "custom-elements.json",
+  "web-types": "./web-types.json",
   "wireit": {
     "types": {
-      "command": "(tsc --build --pretty || true) && npm run types-restore-visibility",
+      "command": "tsc --build --pretty && npm run types-restore-visibility",
       "dependencies": [
         "../singleton-manager:types"
       ],

package/vscode.css-custom-data.json

@@ -0,0 +1,5 @@
+{
+  "version": 1.1,
+  "properties": [],
+  "pseudoElements": []
+}