@lion/ui 0.8.8 → 0.9.1

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

@@ -63,7 +63,7 @@ class MyForm extends LitElement {
 }
 ```
 
-> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/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/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
 
 The 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.
 
@@ -73,7 +73,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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/how-to/#exceptional-cases) below.
+[exceptional cases](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/how-to/#exceptional-cases) below.
 
 ### Exceptional cases
 
@@ -81,8 +81,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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/how-to/create-a-custom-field.md)
-  - follow [extend a native input](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/how-to/extend-a-native-input.md)
+  - follow [create a custom field](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/how-to/create-a-custom-field.md)
+  - follow [extend a native input](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/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

@@ -11,9 +11,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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/components/input/overview.md).
+Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/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/6d2e9975afe83256cc6ee8677841f497bd697512/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/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/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/index.md

@@ -12,9 +12,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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -22,13 +22,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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/how-to/get-started.md)
-- [Create a custom field](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/how-to/create-a-custom-field.md)
-- [Extend a native input](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/how-to/extend-a-native-input.md)
+- [Get started](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/how-to/get-started.md)
+- [Create a custom field](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/how-to/create-a-custom-field.md)
+- [Extend a native input](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/how-to/extend-a-native-input.md)

package/docs/guides/principles/index.md

@@ -12,9 +12,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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -22,5 +22,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/6d2e9975afe83256cc6ee8677841f497bd697512/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/6d2e9975afe83256cc6ee8677841f497bd697512/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/docs/blog/extending-documentation.md)

package/docs/guides/principles/styling.md

@@ -19,7 +19,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/6d2e9975afe83256cc6ee8677841f497bd697512/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/9825cbf65639370f2e4e7bb994e3bc1ba60b0f9a/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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lion/ui",
-  "version": "0.8.8",
+  "version": "0.9.1",
   "description": "A package of extendable web components",
   "license": "MIT",
   "author": "ing-bank",