@lion/ui 0.8.0 → 0.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (89) hide show
  1. package/README.md +7 -7
  2. package/components/form/src/LionForm.js +3 -12
  3. package/components/form/test/lion-form.test.js +88 -1
  4. package/components/form-core/src/registration/FormRegisteringMixin.js +1 -1
  5. package/components/form-core/types/registration/FormRegisteringMixinTypes.ts +1 -1
  6. package/components/listbox/test-suites/ListboxMixin.suite.js +2 -2
  7. package/components/localize/src/LocalizeManager.js +3 -28
  8. package/components/overlays/src/OverlayController.js +1 -1
  9. package/custom-elements.json +107 -171
  10. package/dist-types/components/form/src/LionForm.d.ts.map +1 -1
  11. package/dist-types/components/form/test/lion-form.test.d.ts.map +1 -1
  12. package/dist-types/components/form-core/types/registration/FormRegisteringMixinTypes.d.ts +1 -1
  13. package/dist-types/components/form-integrations/test/helpers/helpers.d.ts +3 -3
  14. package/dist-types/components/form-integrations/test/helpers/helpers.d.ts.map +1 -1
  15. package/dist-types/components/localize/src/LocalizeManager.d.ts +1 -19
  16. package/dist-types/components/localize/src/LocalizeManager.d.ts.map +1 -1
  17. package/dist-types/tsconfig.tsbuildinfo +1 -1
  18. package/docs/components/checkbox-group/api-table.md +2 -2
  19. package/docs/components/checkbox-group/overview.md +2 -2
  20. package/docs/components/collapsible/overview.md +1 -1
  21. package/docs/components/combobox/overview.md +1 -1
  22. package/docs/components/combobox/use-cases.md +1 -1
  23. package/docs/components/dialog/overview.md +1 -1
  24. package/docs/components/fieldset/overview.md +5 -5
  25. package/docs/components/form/overview.md +3 -3
  26. package/docs/components/icon/use-cases.md +1 -1
  27. package/docs/components/input/api-table.md +1 -1
  28. package/docs/components/input/overview.md +1 -1
  29. package/docs/components/input-amount/api-table.md +1 -1
  30. package/docs/components/input-amount/overview.md +3 -3
  31. package/docs/components/input-date/api-table.md +1 -1
  32. package/docs/components/input-date/overview.md +3 -3
  33. package/docs/components/input-datepicker/api-table.md +1 -1
  34. package/docs/components/input-datepicker/overview.md +5 -5
  35. package/docs/components/input-email/api-table.md +1 -1
  36. package/docs/components/input-email/overview.md +2 -2
  37. package/docs/components/input-file/api-table.md +1 -1
  38. package/docs/components/input-file/overview.md +1 -1
  39. package/docs/components/input-iban/api-table.md +1 -1
  40. package/docs/components/input-iban/overview.md +2 -2
  41. package/docs/components/input-range/api-table.md +1 -1
  42. package/docs/components/input-range/overview.md +2 -2
  43. package/docs/components/input-stepper/api-table.md +1 -1
  44. package/docs/components/input-stepper/overview.md +1 -1
  45. package/docs/components/input-tel/api-table.md +1 -1
  46. package/docs/components/input-tel/overview.md +1 -1
  47. package/docs/components/input-tel/use-cases.md +6 -6
  48. package/docs/components/input-tel-dropdown/api-table.md +1 -1
  49. package/docs/components/input-tel-dropdown/overview.md +1 -1
  50. package/docs/components/listbox/api-table.md +1 -1
  51. package/docs/components/listbox/use-cases.md +1 -1
  52. package/docs/components/radio-group/api-table.md +1 -1
  53. package/docs/components/radio-group/overview.md +3 -3
  54. package/docs/components/select/api-table.md +1 -1
  55. package/docs/components/select/use-cases.md +1 -1
  56. package/docs/components/select-rich/use-cases.md +1 -1
  57. package/docs/components/switch/api-table.md +1 -1
  58. package/docs/components/tabs/examples.md +1 -1
  59. package/docs/components/textarea/api-table.md +1 -1
  60. package/docs/fundamentals/index.md +4 -4
  61. package/docs/fundamentals/node-tools/providence-analytics/LocalConfiguration.md +1 -1
  62. package/docs/fundamentals/node-tools/providence-analytics/QueryResult.md +1 -1
  63. package/docs/fundamentals/node-tools/providence-analytics/analyzer.md +1 -1
  64. package/docs/fundamentals/node-tools/providence-analytics/dashboard.md +1 -1
  65. package/docs/fundamentals/node-tools/providence-analytics/overview.md +3 -3
  66. package/docs/fundamentals/node-tools/publish-docs/overview.md +3 -3
  67. package/docs/fundamentals/node-tools/rocket-preset-extend-lion-docs/overview.md +2 -2
  68. package/docs/fundamentals/rationales/accessibility.md +1 -1
  69. package/docs/fundamentals/systems/core/SlotMixin.md +1 -1
  70. package/docs/fundamentals/systems/core/overview.md +1 -1
  71. package/docs/fundamentals/systems/form/api-table.md +1 -1
  72. package/docs/fundamentals/systems/form/formatting-and-parsing.md +4 -4
  73. package/docs/fundamentals/systems/form/model-value.md +1 -1
  74. package/docs/fundamentals/systems/form/overview.md +28 -28
  75. package/docs/fundamentals/systems/form/validate.md +2 -2
  76. package/docs/fundamentals/systems/localize/api-table.md +0 -3
  77. package/docs/fundamentals/systems/localize/overview.md +4 -4
  78. package/docs/fundamentals/systems/overlays/configuration.md +2 -2
  79. package/docs/fundamentals/systems/overlays/overview.md +5 -5
  80. package/docs/fundamentals/systems/overlays/use-cases.md +2 -2
  81. package/docs/fundamentals/tools/helpers/overview.md +1 -1
  82. package/docs/fundamentals/tools/singleton-manager/overview.md +4 -4
  83. package/docs/guides/how-to/create-a-custom-field.md +5 -5
  84. package/docs/guides/how-to/create-a-form.md +4 -4
  85. package/docs/guides/how-to/extend-a-native-input.md +2 -2
  86. package/docs/guides/index.md +8 -8
  87. package/docs/guides/principles/index.md +5 -5
  88. package/docs/guides/principles/styling.md +1 -1
  89. package/package.json +1 -1
package/docs/components/input-tel-dropdown/api-table.md CHANGED
@@ -53,7 +53,7 @@
53
53
  | `placeholder` | public | `string` | `''` | | LionInput |
54
54
  | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection
of the parent. Also, it serves as the key of key/value pairs in
 modelValue/serializedValue objects | LionField |
55
55
  | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or
ChoiceGroup | LionField |
56
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
56
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
57
57
  | `_requestedToBeDisabled` | protected | `boolean` | `false` | | LionField |
58
58
  | `disabled` | public | `boolean` | `false` | | LionField |
59
59
  | `_feedbackConditionMeta` | protected | | | Allows Subclassers to add meta info for feedbackCondition | LionField |
package/docs/components/input-tel-dropdown/overview.md CHANGED
@@ -19,7 +19,7 @@ export const main = () => {
19
19
 
20
20
  ## Features
21
21
 
22
- - Extends our [input-tel](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-tel/overview.md)
22
+ - Extends our [input-tel](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-tel/overview.md)
23
23
  - Shows dropdown list with all possible regions
24
24
  - Shows only allowed regions in dropdown list when .allowedRegions is configured
25
25
  - Highlights regions on top of dropdown list when .preferredRegions is configured
package/docs/components/listbox/api-table.md CHANGED
@@ -215,7 +215,7 @@
215
215
  | `_isHandlingUserInput` | protected | `boolean` | `false` | Flag that will be set when user interaction takes place (for instance after an 'input'
event). Will be added as meta info to the \`model-value-changed\` event. Depending on
whether a user is interacting, formatting logic will be handled differently. | FormatMixin |
216
216
  | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection
of the parent. Also, it serves as the key of key/value pairs in
 modelValue/serializedValue objects | FormRegisteringMixin |
217
217
  | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or
ChoiceGroup | FormRegisteringMixin |
218
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | FormRegisteringMixin |
218
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | FormRegisteringMixin |
219
219
 
220
220
  ### Methods
221
221
 
package/docs/components/listbox/use-cases.md CHANGED
@@ -139,4 +139,4 @@ Navigation will skip over disabled options. Let's disable Artichoke and Brussel
139
139
 
140
140
  ## Validation
141
141
 
142
- A validator can be used to make it e.g. `required`. If you want to know how to do that, please take a look at our [validation examples](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/validate.md).
142
+ A validator can be used to make it e.g. `required`. If you want to know how to do that, please take a look at our [validation examples](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/validate.md).
package/docs/components/radio-group/api-table.md CHANGED
@@ -43,7 +43,7 @@
43
43
  | `placeholder` | public | `string` | `''` | | LionInput |
44
44
  | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection
of the parent. Also, it serves as the key of key/value pairs in
 modelValue/serializedValue objects | LionField |
45
45
  | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or
ChoiceGroup | LionField |
46
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
46
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
47
47
  | `_requestedToBeDisabled` | protected | `boolean` | `false` | | LionField |
48
48
  | `_feedbackConditionMeta` | protected | | | Allows Subclassers to add meta info for feedbackCondition | LionField |
49
49
  | `touched` | public | `boolean` | `false` | True when user has focused and left(blurred) the field. | LionField |
package/docs/components/radio-group/overview.md CHANGED
@@ -20,12 +20,12 @@ export const main = () => html`
20
20
  `;
21
21
  ```
22
22
 
23
- - Make sure that to use a name attribute as it is necessary for our [form](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/form/overview.md)'s serialization result.
24
- - If you have many options for a user to pick from, consider using our [select](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/select/overview.md) instead.
23
+ - Make sure that to use a name attribute as it is necessary for our [form](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/form/overview.md)'s serialization result.
24
+ - If you have many options for a user to pick from, consider using our [select](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/select/overview.md) instead.
25
25
 
26
26
  ## Features
27
27
 
28
- Since it extends from our [fieldset](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/fieldset/overview.md), it has all the features a fieldset has.
28
+ Since it extends from our [fieldset](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/fieldset/overview.md), it has all the features a fieldset has.
29
29
 
30
30
  - Get or set the checked value of the group:
31
31
  - modelValue (default) - `checkedValue()`
package/docs/components/select/api-table.md CHANGED
@@ -26,7 +26,7 @@
26
26
  | `modelValue` | public | | | | LionField |
27
27
  | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection
of the parent. Also, it serves as the key of key/value pairs in
 modelValue/serializedValue objects | LionField |
28
28
  | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or
ChoiceGroup | LionField |
29
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
29
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
30
30
  | `_requestedToBeDisabled` | protected | `boolean` | `false` | | LionField |
31
31
  | `disabled` | public | `boolean` | `false` | | LionField |
32
32
  | `_feedbackConditionMeta` | protected | | | Allows Subclassers to add meta info for feedbackCondition | LionField |
package/docs/components/select/use-cases.md CHANGED
@@ -53,4 +53,4 @@ Or by setting the `disabled` attribute on the entire `lion-select` field.
53
53
 
54
54
  ## Validation
55
55
 
56
- A validator can be used to make it e.g. `required`. If you want to know how to do that, please take a look at our [validation examples](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/validate.md).
56
+ A validator can be used to make it e.g. `required`. If you want to know how to do that, please take a look at our [validation examples](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/validate.md).
package/docs/components/select-rich/use-cases.md CHANGED
@@ -302,7 +302,7 @@ LionSelectRich will give it acces to:
302
302
  - LionSelectRich itself, via `.hostElement`
303
303
 
304
304
  Code of an advanced custom invoker is shown below (this is the code for the
305
- invoker used in [IntlSelectRich](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/select-rich/examples.md)).
305
+ invoker used in [IntlSelectRich](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/select-rich/examples.md)).
306
306
  The invoker is usually added in the invoker slot of the LionSelectRich subclass.
307
307
  However, it would also be possible for an application developer to provide the invoker
308
308
  by putting it in light dom:
package/docs/components/switch/api-table.md CHANGED
@@ -34,7 +34,7 @@
34
34
  | `_isRepropagationEndpoint` | public | `boolean` | `false` | By default, a field with \_repropagationRole 'choice-group' will act as an
'endpoint'. This means it will be considered as an individual field: for
a select, individual options will not be part of the formPath. They
will.
Similarly, components that (a11y wise) need to be fieldsets, but 'interaction wise'
(from Application Developer perspective) need to be more like fields
(think of an amount-input with a currency select box next to it), can set this
to true to hide private internals in the formPath. | LionField |
35
35
  | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection
of the parent. Also, it serves as the key of key/value pairs in
 modelValue/serializedValue objects | LionField |
36
36
  | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or
ChoiceGroup | LionField |
37
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
37
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
38
38
  | `_requestedToBeDisabled` | protected | `boolean` | `false` | | LionField |
39
39
  | `_feedbackConditionMeta` | protected | | | Allows Subclassers to add meta info for feedbackCondition | LionField |
40
40
  | `touched` | public | `boolean` | `false` | True when user has focused and left(blurred) the field. | LionField |
package/docs/components/tabs/examples.md CHANGED
@@ -9,7 +9,7 @@ import './src/lea-tab-panel.js';
9
9
 
10
10
  ## Lea Tabs
11
11
 
12
- Learn how to create the `lea tabs` in our ["introducing lion" blogpost](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/blog/ing-open-sources-lion.md).
12
+ Learn how to create the `lea tabs` in our ["introducing lion" blogpost](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/blog/ing-open-sources-lion.md).
13
13
 
14
14
  ```js preview-story
15
15
  export const main = () => html`
package/docs/components/textarea/api-table.md CHANGED
@@ -42,7 +42,7 @@
42
42
  | `modelValue` | public | | | | LionField |
43
43
  | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection
of the parent. Also, it serves as the key of key/value pairs in
 modelValue/serializedValue objects | LionField |
44
44
  | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or
ChoiceGroup | LionField |
45
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
45
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events
do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.
Use this option if you know what you're doing. It will then be possible to nest FormControls
inside shadow dom. See https\://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
46
46
  | `_requestedToBeDisabled` | protected | `boolean` | `false` | | LionField |
47
47
  | `disabled` | public | `boolean` | `false` | | LionField |
48
48
  | `_feedbackConditionMeta` | protected | | | Allows Subclassers to add meta info for feedbackCondition | LionField |
package/docs/fundamentals/index.md CHANGED
@@ -9,11 +9,11 @@ Here you find more details about what we offer.
9
9
 
10
10
  Let's see what each section describes.
11
11
 
12
- 1. [Systems](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/core/overview.md) <br>
12
+ 1. [Systems](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/core/overview.md) <br>
13
13
  These are the fundamental systems that power all of our components.
14
- 2. [Tools](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/tools/helpers/overview.md) <br>
14
+ 2. [Tools](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/tools/helpers/overview.md) <br>
15
15
  Frontend Tools useful for web development but are not visual and therefore are not components.
16
- 3. [Node Tools](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/babel-plugin-extend-docs/overview.md) <br>
16
+ 3. [Node Tools](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/babel-plugin-extend-docs/overview.md) <br>
17
17
  Node tools to analyse the code and for extending the documentation.
18
- 4. [Rationales](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/rationales/side-effects.md) <br>
18
+ 4. [Rationales](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/rationales/side-effects.md) <br>
19
19
  The reasoning behind some of our decisions.
package/docs/fundamentals/node-tools/providence-analytics/LocalConfiguration.md CHANGED
@@ -45,7 +45,7 @@ export default {
45
45
  ### referenceCollections
46
46
 
47
47
  A list of file system paths. They can be defined relative from the current project root or they can be full paths.
48
- When a [MatchAnalyzer](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/providence-analytics/analyzer.md) like `match-imports` or `match-subclasses` is used, the default reference(s) can be configured here. For instance: ['/path/to/@lion/ui/form.js']
48
+ When a [MatchAnalyzer](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/providence-analytics/analyzer.md) like `match-imports` or `match-subclasses` is used, the default reference(s) can be configured here. For instance: ['/path/to/@lion/ui/form.js']
49
49
 
50
50
  An example:
51
51
 
package/docs/fundamentals/node-tools/providence-analytics/QueryResult.md CHANGED
@@ -108,4 +108,4 @@ QueryOutput structure could be simplified in the future.
108
108
 
109
109
  The output files stored in the file system always need to be machine independent:
110
110
  this means that all machine specific information, like a complete filepath, needs to be removed from a QueryOutput (paths relative from project root are still allowed).
111
- In that way, the caching mechanism (based on hash comparisons) as described in [Analyzer](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/providence-analytics/analyzer.md) is guaranteed to work across different machines.
111
+ In that way, the caching mechanism (based on hash comparisons) as described in [Analyzer](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/providence-analytics/analyzer.md) is guaranteed to work across different machines.
package/docs/fundamentals/node-tools/providence-analytics/analyzer.md CHANGED
@@ -7,7 +7,7 @@ A few examples are:
7
7
  - find-exports
8
8
  - match-imports
9
9
 
10
- An analyzer will give back a [QueryResult](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) that will be written to the file system by Providence.
10
+ An analyzer will give back a [QueryResult](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) that will be written to the file system by Providence.
11
11
  All analyzers need to extend from the `Analyzer` base class, found in `src/program/analyzers/helpers`.
12
12
 
13
13
  ## Public api
package/docs/fundamentals/node-tools/providence-analytics/dashboard.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Node Tools >> Providence Analytics >> Dashboard ||30
2
2
 
3
- An interactive overview of all aggregated [QueryResults](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) can be found in the dashboard.
3
+ An interactive overview of all aggregated [QueryResults](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) can be found in the dashboard.
4
4
  The dashboard is a small nodejs server (based on es-dev-server + middleware) and a frontend
5
5
  application.
6
6
 
package/docs/fundamentals/node-tools/providence-analytics/overview.md CHANGED
@@ -47,7 +47,7 @@ npm i --save-dev providence-analytics
47
47
  You are now ready to use providence in your project. All
48
48
  data will be stored in json files in the folder `./providence-output`
49
49
 
50
- ![CLI](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/providence-analytics/assets/provicli.gif 'CLI')
50
+ ![CLI](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/providence-analytics/assets/provicli.gif 'CLI')
51
51
 
52
52
  ## Setup: Dashboard
53
53
 
@@ -76,7 +76,7 @@ export default {
76
76
 
77
77
  Run `npm run providence:dashboard`
78
78
 
79
- ![dashboard](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/providence-analytics/assets/providash.gif 'dashboard')
79
+ ![dashboard](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/providence-analytics/assets/providash.gif 'dashboard')
80
80
 
81
81
  ## Setup: about result output
82
82
 
@@ -153,7 +153,7 @@ Now you will get a list of all predefined analyzers:
153
153
  - match-subclasses
154
154
  - etc...
155
155
 
156
- ![Analyzer query](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/providence-analytics/assets/analyzer-query.gif 'Analyzer query')
156
+ ![Analyzer query](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/providence-analytics/assets/analyzer-query.gif 'Analyzer query')
157
157
 
158
158
  <!--
159
159
  ## Running providence from its own repo
package/docs/fundamentals/node-tools/publish-docs/overview.md CHANGED
@@ -31,7 +31,7 @@ For a Mono Repository
31
31
  ```md
32
32
  # My Pkg
33
33
 
34
- [=> See Source <=](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/docs/deep/dir/overview.md)
34
+ [=> See Source <=](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/docs/deep/dir/overview.md)
35
35
  ```
36
36
 
37
37
  ## CLI flags
@@ -61,7 +61,7 @@ Bring the `overview.md` in a docs folder along.
61
61
  👉 `packages/[my-package]/docs/overview.md`
62
62
 
63
63
  ```md
64
- [=> See Source <=](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/docs/deep/dir/overview.md)
64
+ [=> See Source <=](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/docs/deep/dir/overview.md)
65
65
  ```
66
66
 
67
67
  Add a `use-cases.md`
@@ -69,7 +69,7 @@ Add a `use-cases.md`
69
69
  👉 `packages/[my-package]/docs/use-cases.md`
70
70
 
71
71
  ```md
72
- [=> See Source <=](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/docs/deep/dir/use-cases.md)
72
+ [=> See Source <=](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/docs/deep/dir/use-cases.md)
73
73
  ```
74
74
 
75
75
  So you will end up with something like this in your package.
package/docs/fundamentals/node-tools/rocket-preset-extend-lion-docs/overview.md CHANGED
@@ -7,7 +7,7 @@ To do this automatically you can use this preset for [rocket](https://rocket.mod
7
7
 
8
8
  ## Features
9
9
 
10
- - Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/remark-extend/overview.md)
10
+ - Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/remark-extend/overview.md)
11
11
  - Renames named imports and all it's usage
12
12
  - Adjusts import paths
13
13
  - Replace tags in template literals
@@ -38,7 +38,7 @@ export default {
38
38
 
39
39
  ## Reusing documentation
40
40
 
41
- To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/node-tools/remark-extend/overview.md).
41
+ To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/node-tools/remark-extend/overview.md).
42
42
 
43
43
  As an example you can create `docs/components/tabs/overview.md`.
44
44
 
package/docs/fundamentals/rationales/accessibility.md CHANGED
@@ -25,4 +25,4 @@ Internally, we delegate all intricacies involved in managing light dom to SlotMi
25
25
  SlotMixin automatically mediates between light dom provided by the user ('public slots') and light dom provided by the component author ('private slots').
26
26
  Also, SlotMixin allows to hook into the reactive update loop of LitElement (automatically rerendering on property changes) and it automatically respects
27
27
  the scoped registry belonging to the shadow root.
28
- More details about SlotMixin can be found in the [SlotMixin documentation](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/core/SlotMixin.md)
28
+ More details about SlotMixin can be found in the [SlotMixin documentation](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/core/SlotMixin.md)
package/docs/fundamentals/systems/core/SlotMixin.md CHANGED
@@ -152,4 +152,4 @@ This will make sure that the slot provided by the user always takes precedence a
152
152
 
153
153
  ### Default slot
154
154
 
155
- As can be seen in the example of [SlotFunctionResults](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/core/#slotfunctionresults), '' can be used to add content to the default slot
155
+ As can be seen in the example of [SlotFunctionResults](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/core/#slotfunctionresults), '' can be used to add content to the default slot
package/docs/fundamentals/systems/core/overview.md CHANGED
@@ -15,7 +15,7 @@ import { LitElement, html, render } from 'lit-element';
15
15
 
16
16
  ## Features
17
17
 
18
- - [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/core/#deduping-of-mixins)
18
+ - [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/core/#deduping-of-mixins)
19
19
  - Mixin to handle disabled (DisabledMixin)
20
20
  - Mixin to handle disabled AND tabIndex (DisabledWithTabIndexMixin)
21
21
  - Mixin to manage auto-generated needed slot elements in light dom (SlotMixin)
package/docs/fundamentals/systems/form/api-table.md CHANGED
@@ -25,7 +25,7 @@
25
25
  | `modelValue` | public | | | | FormControlMixin |
26
26
  | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection&#xA;of the parent. Also, it serves as the key of key/value pairs in&#xA; modelValue/serializedValue objects | FormRegisteringMixin |
27
27
  | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or&#xA;ChoiceGroup | FormRegisteringMixin |
28
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events&#xA;do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.&#xA;Use this option if you know what you're doing. It will then be possible to nest FormControls&#xA;inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | FormRegisteringMixin |
28
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events&#xA;do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.&#xA;Use this option if you know what you're doing. It will then be possible to nest FormControls&#xA;inside shadow dom. See https\://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | FormRegisteringMixin |
29
29
  | `_requestedToBeDisabled` | protected | `boolean` | `false` | | DisabledMixin |
30
30
  | `disabled` | public | `boolean` | `false` | | DisabledMixin |
31
31
  | `touched` | public | `boolean` | `false` | True when user has focused and left(blurred) the field. | InteractionStateMixin |
package/docs/fundamentals/systems/form/formatting-and-parsing.md CHANGED
@@ -23,7 +23,7 @@ Our fields can automatically format/parse/serialize user input or an input set i
23
23
 
24
24
  Below are some concrete examples of implementations of formatters and parsers mimicking a (basic) amount input.
25
25
 
26
- > For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-amount/overview.md).
26
+ > For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-amount/overview.md).
27
27
  > This comes with its own formatter, parser, serializer.
28
28
 
29
29
  ### Parsers & modelValue
@@ -230,16 +230,16 @@ Below we show three flow diagrams to show the flow of formatting, serializing an
230
230
 
231
231
  Where a user changes the input with their keyboard:
232
232
 
233
- ![Standard flow](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
233
+ ![Standard flow](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
234
234
 
235
235
  ### Unparseable flow
236
236
 
237
237
  Where a user sets the input to something that is not parseable by the parser:
238
238
 
239
- ![Unparseable flow](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
239
+ ![Unparseable flow](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
240
240
 
241
241
  ### Imperative / programmatic flow
242
242
 
243
243
  Where the developer sets the modelValue of the input programmatically:
244
244
 
245
- ![Imperative flow](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')
245
+ ![Imperative flow](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')
package/docs/fundamentals/systems/form/model-value.md CHANGED
@@ -21,7 +21,7 @@ level, via:
21
21
  > Internal/private concepts like viewValue, formattedValue, serializedValue are therefore not
22
22
  > recommended as a means of interaction.
23
23
 
24
- For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/formatting-and-parsing.md)
24
+ For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/formatting-and-parsing.md)
25
25
 
26
26
  ### Event meta
27
27
 
package/docs/fundamentals/systems/form/overview.md CHANGED
@@ -20,9 +20,9 @@ Fields (think of an input, textarea, select) are the actual form controls the en
20
20
 
21
21
  On top of this, they feature:
22
22
 
23
- - [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
24
- - Advanced [validation](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/validate.md) possibilities.
25
- - Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/interaction-states.md).
23
+ - [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
24
+ - Advanced [validation](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/validate.md) possibilities.
25
+ - Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/interaction-states.md).
26
26
  - Provision of labels and help texts in an easy, declarative manner.
27
27
  - Accessibility out of the box.
28
28
  - Advanced styling possibilities: map your own Design System to the internal HTML structure.
@@ -31,33 +31,33 @@ On top of this, they feature:
31
31
 
32
32
  ### Platform fields (wrappers)
33
33
 
34
- - [LionInput](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input/overview.md), a wrapper for `<input>`.
35
- - [LionTextarea](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
36
- - [LionSelect](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/select/overview.md), a wrapper for `<select>`.
34
+ - [LionInput](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input/overview.md), a wrapper for `<input>`.
35
+ - [LionTextarea](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
36
+ - [LionSelect](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/select/overview.md), a wrapper for `<select>`.
37
37
 
38
38
  ### Custom fields (wrappers)
39
39
 
40
- Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
40
+ Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
41
41
 
42
- - [LionCombobox](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/combobox/overview.md), a custom implementation of a combobox.
43
- - [LionDate](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
44
- - [LionDatepicker](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
45
- - [LionListbox](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/listbox/overview.md), a custom implementation of a listbox.
46
- - [LionInputAmount](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
47
- - [LionInputEmail](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
48
- - [LionInputIban](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
49
- - [LionInputRange](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
50
- - [LionInputStepper](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
51
- - [LionSelectRich](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
42
+ - [LionCombobox](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/combobox/overview.md), a custom implementation of a combobox.
43
+ - [LionDate](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
44
+ - [LionDatepicker](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
45
+ - [LionListbox](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/listbox/overview.md), a custom implementation of a listbox.
46
+ - [LionInputAmount](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
47
+ - [LionInputEmail](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
48
+ - [LionInputIban](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
49
+ - [LionInputRange](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
50
+ - [LionInputStepper](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
51
+ - [LionSelectRich](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
52
52
 
53
53
  ### Choice Input Fields
54
54
 
55
55
  For form controls which return a `checked-state` you can use the `lion-choice-input` mixin. It is used in:
56
56
 
57
- - [LionCheckbox](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
57
+ - [LionCheckbox](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
58
58
  - LionOption, an alternative for `<option>`.
59
- - [LionRadio](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
60
- - [LionSwitch](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/switch/overview.md), a custom implementation of a switch.
59
+ - [LionRadio](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
60
+ - [LionSwitch](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/switch/overview.md), a custom implementation of a switch.
61
61
 
62
62
  Which contains the following features:
63
63
 
@@ -69,14 +69,14 @@ Which contains the following features:
69
69
 
70
70
  Fieldsets are groups of fields. They can be considered fields on their own as well, since they partly share the normalized API via `FormControlMixin`. Fieldsets are the basis for:
71
71
 
72
- - [LionFieldset](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
73
- - [LionForm](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
74
- - [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
75
- - [LionRadioGroup](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
72
+ - [LionFieldset](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
73
+ - [LionForm](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
74
+ - [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
75
+ - [LionRadioGroup](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
76
76
 
77
77
  ## Other Resources
78
78
 
79
- - [Model Value](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/model-value.md)
80
- - [Formatting and parsing](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/formatting-and-parsing.md)
81
- - [Interaction states](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/interaction-states.md)
82
- - [Validation System](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/validate.md)
79
+ - [Model Value](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/model-value.md)
80
+ - [Formatting and parsing](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/formatting-and-parsing.md)
81
+ - [Interaction states](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/interaction-states.md)
82
+ - [Validation System](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/validate.md)
package/docs/fundamentals/systems/form/validate.md CHANGED
@@ -57,7 +57,7 @@ Validation happens on every change of `modelValue`. A change in modelValue can b
57
57
 
58
58
  ## When validation feedback will be shown
59
59
 
60
- Although validation happens realtime under the hood, displaying validity feedback in realtime may not always lead to the desired User Experience. Together with [interaction states](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/interaction-states.md),
60
+ Although validation happens realtime under the hood, displaying validity feedback in realtime may not always lead to the desired User Experience. Together with [interaction states](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/interaction-states.md),
61
61
  validity states can determine whether a validation message should be shown along the input field.
62
62
 
63
63
  ## Assessing field validation state programmatically
@@ -232,7 +232,7 @@ export const requiredValidator = () => html`
232
232
  `;
233
233
  ```
234
234
 
235
- The default `Required` validation message is "Please, enter a(n) {fieldName}". In which the "fieldName" can be provided separately via the `fieldName` attribute, with a fallback to the label. See [override fieldname](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/form/#override-fieldname) for more information.
235
+ The default `Required` validation message is "Please, enter a(n) {fieldName}". In which the "fieldName" can be provided separately via the `fieldName` attribute, with a fallback to the label. See [override fieldname](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/form/#override-fieldname) for more information.
236
236
 
237
237
  Specific required messages for a select and file-upload are created.
238
238
 
package/docs/fundamentals/systems/localize/api-table.md CHANGED
@@ -38,9 +38,6 @@
38
38
  | `_cacheNamespaceLoaderPromise` | protected | | `locale: string, namespace: string, promise: Promise.<Object\|void>` | | |
39
39
  | `_lookupNamespaceLoader` | protected | | `namespace: string` | `function\|null` | |
40
40
  | `_getLangFromLocale` | protected | | `locale: string` | `string` | |
41
- | `addEventListener` | public | | `type: string, listener: EventListener, options: ...Object` | | |
42
- | `removeEventListener` | public | | `type: string, listener: EventListener, options: ...Object` | | |
43
- | `dispatchEvent` | public | | `event: CustomEvent` | | |
44
41
  | `_onLocaleChanged` | protected | | `newLocale: string, oldLocale: string` | `undefined` | |
45
42
  | `_loadAllMissing` | protected | | `newLocale: string, oldLocale: string` | | |
46
43
  | `_getMessageForKeys` | protected | | `keys: string \| string[], locale: string` | `string \| undefined` | |
package/docs/fundamentals/systems/localize/overview.md CHANGED
@@ -9,15 +9,15 @@ In it's simplest form it is a function that returns the translated text for a na
9
9
  - Formatting of numbers, amounts
10
10
  - Formatting of dates
11
11
 
12
- Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/localize/use-cases.md).
12
+ Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/localize/use-cases.md).
13
13
 
14
14
  ## Content
15
15
 
16
16
  | Feature | Description |
17
17
  | ---------------------------------------- | --------------------------------------------- |
18
- | [Translate Text](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/localize/text.md) | Load and translate text in multiple languages |
19
- | [Format Numbers](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages |
20
- | [Format Dates](https://github.com/ing-bank/lion/blob/370b357bd3ab5667616801c496f59c79d71585ba/docs/fundamentals/systems/localize/dates.md) | Format dates in multiple languages |
18
+ | [Translate Text](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/localize/text.md) | Load and translate text in multiple languages |
19
+ | [Format Numbers](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages |
20
+ | [Format Dates](https://github.com/ing-bank/lion/blob/16681c85e3813fa8dbb91ffcd834466493832d03/docs/fundamentals/systems/localize/dates.md) | Format dates in multiple languages |
21
21
 
22
22
  ## Installation
23
23