@lion/ui 0.8.5 → 0.8.7

package/docs/fundamentals/node-tools/providence-analytics/overview.md

@@ -2,7 +2,6 @@
 
 ```js script
 import { html } from '@mdjs/mdjs-preview';
-import { providenceFlowSvg, providenceInternalFlowSvg } from './assets/_mermaid.svg.js';
 ```
 
 Providence is the 'All Seeing Eye' that generates usage statistics by analyzing code.
@@ -10,8 +9,6 @@ It measures the effectivity and popularity of your software.
 With just a few commands you can measure the impact for (breaking) changes, making
 your release process more stable and predictable.
 
-Providence can be used as a dev dependency in a project for which metrics
-can be generated via analyzers (see below).
 For instance for a repo "lion-based-ui" that extends @lion/\* we can answer questions like:
 
 - **Which subsets of my product are popular?**
@@ -23,170 +20,76 @@ For instance for a repo "lion-based-ui" that extends @lion/\* we can answer ques
 
 - etc...
 
-All the above results can be shown in a dashboard (see below), which allows to sort exports from reference project (@lion) based on popularity, category, consumer etc.
-The dashboard allows to aggregate data from many target projects as well and will show you on a detailed (file) level how those components are being consumed by which projects.
+Providence uses abstract syntax trees (ASTs) to have the most advanced analysis possible.
+It does this via the [oxc parser](https://oxc.rs/docs/guide/usage/parser.html), the quickest parser available today!
 
-## Setup
+## Run
 
-### Install providence
+Providence expects an analyzer name that tells it what type of analysis to run:
 
 ```bash
-npm i --save-dev providence-analytics
+npx providence analyze <analyzer-name>
 ```
 
-### Add a providence script to package.json
+By default Providence ships these analyzers:
 
-```json
-"scripts": {
-  "providence:match-imports": "providence analyze match-imports -r 'node_modules/@lion/ui/*.js'",
-}
-```
-
-> The example above illustrates how to run the "match-imports" analyzer for reference project 'lion-based-ui'. Note that it is possible to run other analyzers and configurations supported by providence as well. For a full overview of cli options, run `npx providence --help`. All supported analyzers will be viewed when running `npx providence analyze`
-
-You are now ready to use providence in your project. All
-data will be stored in json files in the folder `./providence-output`
-
-![CLI](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/node-tools/providence-analytics/assets/provicli.gif 'CLI')
-
-## Setup: Dashboard
-
-### Add "providence:dashboard" script to package.json
-
-```js
-...
-"scripts": {
-    ...
-    "providence:dashboard": "providence dashboard"
-}
-```
-
-### Add providence.conf.js
-
-```js
-export default {
-  referenceCollections: {
-    'lion-based-ui-collection': [
-      './node_modules/lion-based-ui/packages/x',
-      './node_modules/lion-based-ui/packages/y',
-    ],
-  },
-};
-```
-
-Run `npm run providence:dashboard`
-
-![dashboard](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/node-tools/providence-analytics/assets/providash.gif 'dashboard')
-
-## Setup: about result output
-
-All output files will be stored in `./providence-output`.
-This means they will be committed to git, so your colleagues don't have to
-rerun the analysis (for large projects with many dependencies this can be time consuming)
-and can directly start the dashboard usage metrics.
-Also, note that the files serve as cache (they are stored with hashes based on project version and analyzer configuration). This means that an interrupted analysis can be
-resumed later on.
-
-## Conceptual overview
-
-Providence performs queries on one or more search targets.
-These search targets consist of one or more software projects (javascript/html repositories)
-
-The diagram below shows how `providenceMain` function can be used from an external context.
-
-```js story
-export const providenceFlow = () => providenceFlowSvg;
-```
-
-## Flow inside providence
-
-The diagram below depicts the flow inside the `providenceMain` function.
-It uses:
-
-- InputDataService
-  Used to create a data structure based on a folder (for instance the search target or
-  the references root). The structure creates entries for every file, which get enriched with code,
-  ast results, query results etc. Returns `InputData` object.
-- QueryService
-  Requires a `queryConfig` and `InputData` object. It will perform a query (grep search or ast analysis)
-  and returns a `QueryResult`.
-  It also contains helpers for the creation of a `queryConfig`
-- ReportService
-  The result gets outputted to the user. Currently, a log to the console and/or a dump to a json file
-  are available as output formats.
-
-```js story
-export const providenceInternalFlow = () => providenceInternalFlowSvg;
-```
-
-## Queries
-
-Providence requires a queries as input.
-Queries are defined as objects and can be of two types:
-
-- feature-query
-- ast-analyzer
-
-A `QueryConfig` is required as input to run the `providenceMain` function.
-This object specifies the type of query and contains the relevant meta
-information that will later be outputted in the `QueryResult` (the JSON object that
-the `providenceMain` function returns.)
-
-## Analyzer Query
-
-Analyzer queries are also created via `QueryConfig`s.
-
-Analyzers can be described as predefined queries that use AST traversal.
+- find-imports
+- find-exports
+- find-classes
+- match-imports
+- match-subclasses
 
-Run:
+Let's say we run `find-imports`:
 
 ```bash
-providence analyze
+npx providence analyze find-imports
 ```
 
-Now you will get a list of all predefined analyzers:
+Now it retrieves all relevant data about es module imports.
+There are plenty of edge cases that it needs to take into account here;
+you can have a look at the tests to get an idea about all different cases Providence handles for you.
 
-- find-imports
-- find-exports
-- find-classes
-- match-imports
-- match-subclasses
-- etc...
+## Projects
+
+Providence uses the concept of projects. A project is a piece of software to analyze:
+usually an npm artifact or a git (mono-)repository. What all projects have in common,
+is a package.json. From it, the following project data is derived:
 
-![Analyzer query](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/node-tools/providence-analytics/assets/analyzer-query.gif 'Analyzer query')
+- the name
+- the version
+- the files it uses for scanning. One of the following strategies is usually followed:
+  - exportmap entrypoints (by 'expanding' package.json "exports" on file system)
+  - npm files (it reads package.json "files" | .npmignore)
+  - the git files (it reads .gitignore)
+  - a custom defined list
 
-<!--
-## Running providence from its own repo
+For a "find" analyzer, there is one project involved (the target project).
 
-### How to add a new search target project
+We can specify it like this (we override the default current working directory):
 
 ```bash
-git submodule add <git-url> ./providence-input-data/search-targets/<project-name>
+npx providence analyze find-imports -t /importing/project
 ```
 
-### How to add a reference project
-
-By adding a reference project, you can automatically see how code in your reference project is
-used across the search target projects.
-Under the hood, this automatically creates a set of queries for you.
+For a "match" analyzer, there is also a reference project.
+Here we match the exports of the reference project (-r) against the imports of the target project (-t).
 
 ```bash
-git submodule add <git-url> ./providence-input-data/references/<project-name>
+npx providence analyze match-imports -t /importing/project -r /exporting/project
 ```
 
-### Updating submodules
+## Utils
 
-Please run:
+Providence comes with many tools for deep traversal of identifiers,
+the (babel like) traversal of ast trees in oxc and swc and more.
+Also more generic utils for caching and performant globbing come delivered with Providence.
 
-```bash
-git submodule update --init --recursive
-```
+For a better understanding, check out the utils folders (tests and code).
 
-### Removing submodules
+## More
 
-Please run:
+For more options, see:
 
 ```bash
-sh ./rm-submodule.sh <path/to/submodule>
+npx providence --help
 ```
--->

package/docs/fundamentals/node-tools/publish-docs/overview.md

@@ -31,7 +31,7 @@ For a Mono Repository
    ```md
    # My Pkg
 
-   [=> See Source <=](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/docs/deep/dir/overview.md)
+   [=> See Source <=](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/docs/deep/dir/overview.md)
    ```
 
 ## CLI flags
@@ -61,7 +61,7 @@ Bring the `overview.md` in a docs folder along.
 👉 `packages/[my-package]/docs/overview.md`
 
 ```md
-[=> See Source <=](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/docs/deep/dir/overview.md)
+[=> See Source <=](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/docs/deep/dir/overview.md)
 ```
 
 Add a `use-cases.md`
@@ -69,7 +69,7 @@ Add a `use-cases.md`
 👉 `packages/[my-package]/docs/use-cases.md`
 
 ```md
-[=> See Source <=](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/docs/deep/dir/use-cases.md)
+[=> See Source <=](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/docs/deep/dir/use-cases.md)
 ```
 
 So you will end up with something like this in your package.

package/docs/fundamentals/node-tools/rocket-preset-extend-lion-docs/overview.md

@@ -7,7 +7,7 @@ To do this automatically you can use this preset for [rocket](https://rocket.mod
 
 ## Features
 
-- Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/node-tools/remark-extend/overview.md)
+- Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/node-tools/remark-extend/overview.md)
 - Renames named imports and all it's usage
 - Adjusts import paths
 - Replace tags in template literals
@@ -38,7 +38,7 @@ export default {
 
 ## Reusing documentation
 
-To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/node-tools/remark-extend/overview.md).
+To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/node-tools/remark-extend/overview.md).
 
 As an example you can create `docs/components/tabs/overview.md`.
 

package/docs/fundamentals/rationales/accessibility.md

@@ -25,4 +25,4 @@ Internally, we delegate all intricacies involved in managing light dom to SlotMi
 SlotMixin automatically mediates between light dom provided by the user ('public slots') and light dom provided by the component author ('private slots').
 Also, SlotMixin allows to hook into the reactive update loop of LitElement (automatically rerendering on property changes) and it automatically respects
 the scoped registry belonging to the shadow root.
-More details about SlotMixin can be found in the [SlotMixin documentation](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/core/SlotMixin.md)
+More details about SlotMixin can be found in the [SlotMixin documentation](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/core/SlotMixin.md)

package/docs/fundamentals/systems/core/SlotMixin.md

@@ -152,4 +152,4 @@ This will make sure that the slot provided by the user always takes precedence a
 
 ### Default slot
 
-As can be seen in the example of [SlotFunctionResults](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/core/#slotfunctionresults), '' can be used to add content to the default slot
+As can be seen in the example of [SlotFunctionResults](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/core/#slotfunctionresults), '' can be used to add content to the default slot

package/docs/fundamentals/systems/core/overview.md

@@ -15,7 +15,7 @@ import { LitElement, html, render } from 'lit-element';
 
 ## Features
 
-- [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/core/#deduping-of-mixins)
+- [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/core/#deduping-of-mixins)
 - Mixin to handle disabled (DisabledMixin)
 - Mixin to handle disabled AND tabIndex (DisabledWithTabIndexMixin)
 - Mixin to manage auto-generated needed slot elements in light dom (SlotMixin)

package/docs/fundamentals/systems/form/formatting-and-parsing.md

@@ -23,7 +23,7 @@ Our fields can automatically format/parse/serialize user input or an input set i
 
 Below are some concrete examples of implementations of formatters and parsers mimicking a (basic) amount input.
 
-> For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-amount/overview.md).
+> For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-amount/overview.md).
 > This comes with its own formatter, parser, serializer.
 
 ### Parsers & modelValue
@@ -230,16 +230,16 @@ Below we show three flow diagrams to show the flow of formatting, serializing an
 
 Where a user changes the input with their keyboard:
 
-![Standard flow](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
+![Standard flow](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
 
 ### Unparseable flow
 
 Where a user sets the input to something that is not parseable by the parser:
 
-![Unparseable flow](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
+![Unparseable flow](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
 
 ### Imperative / programmatic flow
 
 Where the developer sets the modelValue of the input programmatically:
 
-![Imperative flow](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')
+![Imperative flow](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')

package/docs/fundamentals/systems/form/model-value.md

@@ -21,7 +21,7 @@ level, via:
 > Internal/private concepts like viewValue, formattedValue, serializedValue are therefore not
 > recommended as a means of interaction.
 
-For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/formatting-and-parsing.md)
+For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/formatting-and-parsing.md)
 
 ### Event meta
 

package/docs/fundamentals/systems/form/overview.md

@@ -20,9 +20,9 @@ Fields (think of an input, textarea, select) are the actual form controls the en
 
 On top of this, they feature:
 
-- [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
-- Advanced [validation](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/validate.md) possibilities.
-- Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/interaction-states.md).
+- [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
+- Advanced [validation](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/validate.md) possibilities.
+- Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/interaction-states.md).
 - Provision of labels and help texts in an easy, declarative manner.
 - Accessibility out of the box.
 - Advanced styling possibilities: map your own Design System to the internal HTML structure.
@@ -31,33 +31,33 @@ On top of this, they feature:
 
 ### Platform fields (wrappers)
 
-- [LionInput](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input/overview.md), a wrapper for `<input>`.
-- [LionTextarea](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
-- [LionSelect](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/select/overview.md), a wrapper for `<select>`.
+- [LionInput](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input/overview.md), a wrapper for `<input>`.
+- [LionTextarea](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
+- [LionSelect](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/select/overview.md), a wrapper for `<select>`.
 
 ### Custom fields (wrappers)
 
-Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
+Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
 
-- [LionCombobox](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/combobox/overview.md), a custom implementation of a combobox.
-- [LionDate](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
-- [LionDatepicker](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
-- [LionListbox](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/listbox/overview.md), a custom implementation of a listbox.
-- [LionInputAmount](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
-- [LionInputEmail](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
-- [LionInputIban](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
-- [LionInputRange](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
-- [LionInputStepper](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
-- [LionSelectRich](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
+- [LionCombobox](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/combobox/overview.md), a custom implementation of a combobox.
+- [LionDate](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
+- [LionDatepicker](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
+- [LionListbox](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/listbox/overview.md), a custom implementation of a listbox.
+- [LionInputAmount](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
+- [LionInputEmail](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
+- [LionInputIban](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
+- [LionInputRange](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
+- [LionInputStepper](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
+- [LionSelectRich](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
 
 ### Choice Input Fields
 
 For form controls which return a `checked-state` you can use the `lion-choice-input` mixin. It is used in:
 
-- [LionCheckbox](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
+- [LionCheckbox](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
 - LionOption, an alternative for `<option>`.
-- [LionRadio](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
-- [LionSwitch](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/switch/overview.md), a custom implementation of a switch.
+- [LionRadio](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
+- [LionSwitch](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/switch/overview.md), a custom implementation of a switch.
 
 Which contains the following features:
 
@@ -69,14 +69,14 @@ Which contains the following features:
 
 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:
 
-- [LionFieldset](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
-- [LionForm](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
-- [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
-- [LionRadioGroup](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
+- [LionFieldset](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
+- [LionForm](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
+- [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
+- [LionRadioGroup](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
 
 ## Other Resources
 
-- [Model Value](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/model-value.md)
-- [Formatting and parsing](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/formatting-and-parsing.md)
-- [Interaction states](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/interaction-states.md)
-- [Validation System](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/validate.md)
+- [Model Value](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/model-value.md)
+- [Formatting and parsing](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/formatting-and-parsing.md)
+- [Interaction states](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/interaction-states.md)
+- [Validation System](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/validate.md)

package/docs/fundamentals/systems/form/validate.md

@@ -57,7 +57,7 @@ Validation happens on every change of `modelValue`. A change in modelValue can b
 
 ## When validation feedback will be shown
 
-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/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/interaction-states.md),
+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/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/interaction-states.md),
 validity states can determine whether a validation message should be shown along the input field.
 
 ## Assessing field validation state programmatically
@@ -232,7 +232,7 @@ export const requiredValidator = () => html`
 `;
 ```
 
-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/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/form/#override-fieldname) for more information.
+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/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/form/#override-fieldname) for more information.
 
 Specific required messages for a select and file-upload are created.
 

package/docs/fundamentals/systems/localize/overview.md

@@ -9,15 +9,15 @@ In it's simplest form it is a function that returns the translated text for a na
 - Formatting of numbers, amounts
 - Formatting of dates
 
-Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/localize/use-cases.md).
+Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/localize/use-cases.md).
 
 ## Content
 
 | Feature                                  | Description                                   |
 | ---------------------------------------- | --------------------------------------------- |
-| [Translate Text](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/localize/text.md)    | Load and translate text in multiple languages |
-| [Format Numbers](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages          |
-| [Format Dates](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/localize/dates.md)     | Format dates in multiple languages            |
+| [Translate Text](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/localize/text.md)    | Load and translate text in multiple languages |
+| [Format Numbers](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages          |
+| [Format Dates](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/localize/dates.md)     | Format dates in multiple languages            |
 
 ## Installation
 

package/docs/fundamentals/systems/overlays/configuration.md

@@ -69,7 +69,7 @@ export const placementGlobal = () => {
 
 ## isTooltip (placementMode: 'local')
 
-As specified in the [overlay rationale](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/overlays/rationale.md) there are only two official types of overlays: dialogs and tooltips. And their main differences are:
+As specified in the [overlay rationale](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/overlays/rationale.md) there are only two official types of overlays: dialogs and tooltips. And their main differences are:
 
 - Dialogs have a modal option, tooltips don’t
 - Dialogs have interactive content, tooltips don’t
@@ -400,7 +400,7 @@ Features:
 
 > Popper strictly is scoped on positioning. **It does not change the dimensions of the content node nor the invoker node**.
 > This also means that if you use the arrow feature, you are in charge of styling it properly, use the data-popper-placement attribute for this.
-> An example implementation can be found in [lion-tooltip](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/tooltip/overview.md), where an arrow is set by default.
+> An example implementation can be found in [lion-tooltip](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/tooltip/overview.md), where an arrow is set by default.
 
 To override the default options we set for local mode, you add a `popperConfig` object to the config passed to the OverlayController.
 Here's a succinct overview of some often used popper properties:

package/docs/fundamentals/systems/overlays/overview.md

@@ -6,7 +6,7 @@ Manages their position on the screen relative to other elements, including other
 
 Its purpose is to make it easy to use our Overlay System declaratively. It can be easily extended where needed, to override event listeners and more.
 
-See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/components/tooltip/overview.md) for example Web Component implementations using the Overlay System.
+See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/components/tooltip/overview.md) for example Web Component implementations using the Overlay System.
 
 ## Features
 
@@ -18,9 +18,9 @@ See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](htt
 - lion-overlay web component:
   - Show content when clicking the invoker
   - Have a `.config` object to set or update the OverlayController's configuration
-- [**OverlaysManager**](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/overlays/use-cases.md#overlaysmanager), a global repository keeping track of all different types of overlays
-- [**OverlayController**](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
-- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/overlays/use-cases.md#overlaymixin), a mixin that can be used to create webcomponents that use the OverlayController under the hood
+- [**OverlaysManager**](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/overlays/use-cases.md#overlaysmanager), a global repository keeping track of all different types of overlays
+- [**OverlayController**](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
+- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/overlays/use-cases.md#overlaymixin), a mixin that can be used to create webcomponents that use the OverlayController under the hood
 
 Usually you will use `lion-dialog` (or `lion-tooltip` if this makes more sense).
 
@@ -110,4 +110,4 @@ class MyOverlayComponent extends OverlayMixin(LitElement) {
 
 ## Rationales
 
-Please check the [system rationals](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/overlays/rationale.md) folder, where we go more in-depth.
+Please check the [system rationals](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/overlays/rationale.md) folder, where we go more in-depth.

package/docs/fundamentals/systems/overlays/use-cases.md

@@ -21,7 +21,7 @@ The overlay system allows to create different types of overlays like dialogs, to
 It's designed to be highly flexible, while still delivering sensible defaults.
 On top of this, the system was built having accessibility in mind.
 
-For a detailed rationale, please consult [Rationale](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/overlays/rationale.md).
+For a detailed rationale, please consult [Rationale](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/overlays/rationale.md).
 
 ```js preview-story
 export const main = () => html`
@@ -69,7 +69,7 @@ Global refers to overlays where the content is positioned in a global root node
 
 Overlays can be configured in many ways to suit your needs. We go in-depth into each option in the Overlay System - Configuration chapter.
 
-We also export a few [preset configuration objects](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/systems/overlays/configuration.md).
+We also export a few [preset configuration objects](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/systems/overlays/configuration.md).
 
 - withModalDialogConfig
 - withDropdownConfig

package/docs/fundamentals/tools/helpers/overview.md

@@ -9,7 +9,7 @@ Therefore, they may not have the same quality standards as our other packages.
 
 | Package                                | Description             |
 | -------------------------------------- | ----------------------- |
-| [sb-action-logger](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/tools/helpers/action-logger.md) | Storybook action logger |
+| [sb-action-logger](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/tools/helpers/action-logger.md) | Storybook action logger |
 
 ## Installation
 

package/docs/fundamentals/tools/singleton-manager/overview.md

@@ -9,7 +9,7 @@ Primarily useful if two major version of a package with a singleton is used.
 npm i --save singleton-manager
 ```
 
-⚠️ You need to make SURE that only ONE version of `singleton-manager` is installed. For how see [Non Goals](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/tools/singleton-manager/#non-goals).
+⚠️ You need to make SURE that only ONE version of `singleton-manager` is installed. For how see [Non Goals](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/tools/singleton-manager/#non-goals).
 
 ### Example Singleton Users
 
@@ -159,7 +159,7 @@ Steps to reproduce:
 1. Page A click on block
 2. Page B => "Blocked: false" (even when hitting the refresh button)
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/tools/singleton-manager/example-fail/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/tools/singleton-manager/example-fail/index.md). <br>
 ➡️ See [the code](https://github.com/ing-bank/lion/tree/master/docs/fundamentals/tools/singleton-manager/example-fail/demo-app.js).
 
 ---
@@ -202,7 +202,7 @@ See it in action
 npm run start:singleton
 ```
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/tools/singleton-manager/example-success/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/tools/singleton-manager/example-success/index.md). <br>
 ➡️ See [the code](https://github.com/ing-bank/lion/tree/master/docs/fundamentals/tools/singleton-manager/example-success/demo-app.js).
 
 ---
@@ -243,7 +243,7 @@ See it in action
 npm run start:singleton-complex
 ```
 
-➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/8dc51c1066421b9b482f2d9964afcbfa9ce2f730/docs/fundamentals/tools/singleton-manager/example-complex/index.md). <br>
+➡️ See [it on the example page](https://github.com/ing-bank/lion/blob/104c49449ebf5b60a1aa22a05e1a9ed8562bd6aa/docs/fundamentals/tools/singleton-manager/example-complex/index.md). <br>
 ➡️ See [the code](https://github.com/ing-bank/lion/tree/master/docs/fundamentals/tools/singleton-manager/example-complex/demo-app.js).
 
 ---