Merge pull request #1620 from ing-bank/changeset-release/master
Version Packages
This commit is contained in:
Thijs Louisse
GitHub
commit
5ab5e8e68c
104 changed files with 3065 additions and 380 deletions
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/input-tel-dropdown': minor
|
||||
---
|
||||
|
||||
New component LionInpuTelDropdown
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/validate-messages': patch
|
||||
---
|
||||
|
||||
fix(validate-messages): typo IsData message
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/form-core': patch
|
||||
---
|
||||
|
||||
FormControl: allow a label-sr-only flag to provide visually hidden labels
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/form-core': patch
|
||||
---
|
||||
|
||||
form-core: expose 'mimicUserInput' test-helper
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/core': patch
|
||||
---
|
||||
|
||||
SlotMixin: support scoped elements
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/tabs': patch
|
||||
---
|
||||
|
||||
tabs: allow to be initialized withhout children
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
---
|
||||
'providence-analytics': minor
|
||||
'publish-docs': minor
|
||||
'remark-extend': minor
|
||||
'rocket-preset-extend-lion-docs': minor
|
||||
'@lion/accordion': minor
|
||||
'@lion/button': minor
|
||||
'@lion/calendar': minor
|
||||
'@lion/checkbox-group': minor
|
||||
'@lion/collapsible': minor
|
||||
'@lion/combobox': minor
|
||||
'@lion/core': minor
|
||||
'@lion/dialog': minor
|
||||
'@lion/fieldset': minor
|
||||
'@lion/form': minor
|
||||
'@lion/form-core': minor
|
||||
'@lion/form-integrations': minor
|
||||
'@lion/icon': minor
|
||||
'@lion/input': minor
|
||||
'@lion/input-amount': minor
|
||||
'@lion/input-date': minor
|
||||
'@lion/input-datepicker': minor
|
||||
'@lion/input-email': minor
|
||||
'@lion/input-iban': minor
|
||||
'@lion/input-range': minor
|
||||
'@lion/input-stepper': minor
|
||||
'@lion/listbox': minor
|
||||
'@lion/localize': minor
|
||||
'@lion/overlays': minor
|
||||
'@lion/pagination': minor
|
||||
'@lion/progress-indicator': minor
|
||||
'@lion/radio-group': minor
|
||||
'@lion/select': minor
|
||||
'@lion/select-rich': minor
|
||||
'@lion/steps': minor
|
||||
'@lion/switch': minor
|
||||
'@lion/tabs': minor
|
||||
'@lion/textarea': minor
|
||||
'@lion/tooltip': minor
|
||||
'@lion/validate-messages': minor
|
||||
---
|
||||
|
||||
New documentation structure
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/overlays': patch
|
||||
---
|
||||
|
||||
Fix check for css typed object support
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/form-core': minor
|
||||
---
|
||||
|
||||
Validation: allow enums as outcome of a Validator
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/input-tel': minor
|
||||
---
|
||||
|
||||
New component "LionInputTel"
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
---
|
||||
'@lion/core': minor
|
||||
'@lion/form-core': minor
|
||||
'@lion/listbox': minor
|
||||
'@lion/select-rich': minor
|
||||
'@lion/switch': minor
|
||||
'@lion/accordion': minor
|
||||
'@lion/ajax': minor
|
||||
'@lion/button': minor
|
||||
'@lion/calendar': minor
|
||||
'@lion/checkbox-group': minor
|
||||
'@lion/collapsible': minor
|
||||
'@lion/combobox': minor
|
||||
'@lion/dialog': minor
|
||||
'@lion/fieldset': minor
|
||||
'@lion/form': minor
|
||||
'@lion/form-integrations': minor
|
||||
'@lion/helpers': minor
|
||||
'@lion/icon': minor
|
||||
'@lion/input': minor
|
||||
'@lion/input-amount': minor
|
||||
'@lion/input-date': minor
|
||||
'@lion/input-datepicker': minor
|
||||
'@lion/input-email': minor
|
||||
'@lion/input-iban': minor
|
||||
'@lion/input-range': minor
|
||||
'@lion/input-stepper': minor
|
||||
'@lion/input-tel': minor
|
||||
'@lion/input-tel-dropdown': minor
|
||||
'@lion/localize': minor
|
||||
'@lion/overlays': minor
|
||||
'@lion/pagination': minor
|
||||
'@lion/progress-indicator': minor
|
||||
'@lion/radio-group': minor
|
||||
'@lion/select': minor
|
||||
'@lion/steps': minor
|
||||
'@lion/tabs': minor
|
||||
'@lion/textarea': minor
|
||||
'@lion/tooltip': minor
|
||||
'@lion/validate-messages': minor
|
||||
---
|
||||
|
||||
BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/form-core': minor
|
||||
---
|
||||
|
||||
Updated the ValidateMixin \_\_setupValidators method to sync the calendar date with validator params with reference to this issue : https://github.com/ing-bank/lion/pull/1641/files#diff-bed9319548b16e509dd4a5c3d9c7c31175b577f91e433ee55a945e05339d2796R632
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'providence-analytics': patch
|
||||
---
|
||||
|
||||
providence-analytics: expose skipCheckMatchCompatibility: skips semver checks when targets and reference projects are matched. Handy for forward compatible libs and libs below v1
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/validate-messages': patch
|
||||
---
|
||||
|
||||
validate-messages: PhoneNumber messages
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/input-datepicker': minor
|
||||
---
|
||||
|
||||
Added a fix by overriding the \_\_onValidatorUpdated() to sync the calendar dates when the validator params got changed
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/listbox': patch
|
||||
---
|
||||
|
||||
Fix: Prevent default behavior while scrolling using arrow keys in a horizontal listbox
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@lion/validate-messages': patch
|
||||
---
|
||||
|
||||
Fixed en-PH default validation message
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'providence-analytics': patch
|
||||
---
|
||||
|
||||
providence-analytics: enhanced allowlistMode detection
|
||||
|
|
@ -1,5 +1,16 @@
|
|||
# Change Log
|
||||
|
||||
## 0.13.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- ab7cc1e0: providence-analytics: expose skipCheckMatchCompatibility: skips semver checks when targets and reference projects are matched. Handy for forward compatible libs and libs below v1
|
||||
- 17dadabf: providence-analytics: enhanced allowlistMode detection
|
||||
|
||||
## 0.12.5
|
||||
|
||||
### Patch Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "providence-analytics",
|
||||
"version": "0.12.5",
|
||||
"version": "0.13.0",
|
||||
"description": "Providence is the 'All Seeing Eye' that measures effectivity and popularity of software. Release management will become highly efficient due to an accurate impact analysis of (breaking) changes",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,11 @@
|
|||
# publish-docs
|
||||
|
||||
## 0.2.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
|
||||
## 0.1.3
|
||||
|
||||
### Patch Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "publish-docs",
|
||||
"version": "0.1.3",
|
||||
"version": "0.2.0",
|
||||
"description": "A tool that copies and processes your documentation (in a monorepo) so it can be published/shipped with your package.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,11 @@
|
|||
# Change Log
|
||||
|
||||
## 0.5.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
|
||||
## 0.4.4
|
||||
|
||||
### Patch Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "remark-extend",
|
||||
"version": "0.4.4",
|
||||
"version": "0.5.0",
|
||||
"description": "A plugin for remark that allows to extend a md file with another md file",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,16 @@
|
|||
# rocket-preset-extend-lion-docs
|
||||
|
||||
## 0.3.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [672c8e99]
|
||||
- remark-extend@0.5.0
|
||||
|
||||
## 0.2.2
|
||||
|
||||
### Patch Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "rocket-preset-extend-lion-docs",
|
||||
"version": "0.2.2",
|
||||
"version": "0.3.0",
|
||||
"description": "A rocket preset to reuse lion documentation inside your design system extension",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -32,7 +32,7 @@
|
|||
"babel-plugin-extend-docs": "0.5.3",
|
||||
"es-module-lexer": "^0.3.6",
|
||||
"plugins-manager": "^0.3.0",
|
||||
"remark-extend": "0.4.4",
|
||||
"remark-extend": "0.5.0",
|
||||
"unist-util-visit": "^2.0.2"
|
||||
},
|
||||
"keywords": [
|
||||
|
|
|
|||
|
|
@ -1,5 +1,74 @@
|
|||
# Change Log
|
||||
|
||||
## 0.9.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.8.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/accordion",
|
||||
"version": "0.8.0",
|
||||
"version": "0.9.0",
|
||||
"description": "Vertically stacked list of invokers that can be clicked to reveal or hide content associated with them.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,7 +36,7 @@
|
|||
"lion-accordion.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0"
|
||||
"@lion/core": "^0.22.0"
|
||||
},
|
||||
"keywords": [
|
||||
"accordion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,66 @@
|
|||
# Change Log
|
||||
|
||||
## 0.14.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
## 0.13.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/ajax",
|
||||
"version": "0.13.0",
|
||||
"version": "0.14.0",
|
||||
"description": "Thin wrapper around fetch with support for interceptors.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,74 @@
|
|||
# Change Log
|
||||
|
||||
## 0.17.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.16.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/button",
|
||||
"version": "0.16.0",
|
||||
"version": "0.17.0",
|
||||
"description": "A button that is easily styleable and accessible in all contexts",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -39,7 +39,7 @@
|
|||
"define.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0"
|
||||
"@lion/core": "^0.22.0"
|
||||
},
|
||||
"keywords": [
|
||||
"button",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,75 @@
|
|||
# Change Log
|
||||
|
||||
## 0.19.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.18.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/calendar",
|
||||
"version": "0.18.0",
|
||||
"version": "0.19.0",
|
||||
"description": "Standalone calendar",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,8 +36,8 @@
|
|||
"lion-calendar.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/localize": "^0.23.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/localize": "^0.24.0"
|
||||
},
|
||||
"keywords": [
|
||||
"calendar",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,80 @@
|
|||
# Change Log
|
||||
|
||||
## 0.20.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
|
||||
## 0.19.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/checkbox-group",
|
||||
"version": "0.19.0",
|
||||
"version": "0.20.0",
|
||||
"description": "A container for multiple checkboxes",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -39,9 +39,9 @@
|
|||
"lion-checkbox-indeterminate.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0"
|
||||
},
|
||||
"keywords": [
|
||||
"checkbox-group",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,74 @@
|
|||
# Change Log
|
||||
|
||||
## 0.8.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.7.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/collapsible",
|
||||
"version": "0.7.0",
|
||||
"version": "0.8.0",
|
||||
"description": "This component is a combination of a button (the invoker), a chunk of extra content.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -38,7 +38,7 @@
|
|||
"demo/custom-collapsible.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0"
|
||||
"@lion/core": "^0.22.0"
|
||||
},
|
||||
"keywords": [
|
||||
"collapsible",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,83 @@
|
|||
# Change Log
|
||||
|
||||
## 0.10.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [d46b9894]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [1ea9f291]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/listbox@0.13.0
|
||||
- @lion/overlays@0.32.0
|
||||
|
||||
## 0.9.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/combobox",
|
||||
"version": "0.9.0",
|
||||
"version": "0.10.0",
|
||||
"description": "A widget made up of a single-line textbox and an associated pop-up listbox element",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -45,10 +45,10 @@
|
|||
"docs/google-combobox/google-combobox.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/listbox": "^0.12.0",
|
||||
"@lion/overlays": "^0.31.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/listbox": "^0.13.0",
|
||||
"@lion/overlays": "^0.32.0"
|
||||
},
|
||||
"keywords": [
|
||||
"combobox",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,71 @@
|
|||
# Change Log
|
||||
|
||||
## 0.22.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- 66531e3c: SlotMixin: support scoped elements
|
||||
|
||||
## 0.21.1
|
||||
|
||||
### Patch Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/core",
|
||||
"version": "0.21.1",
|
||||
"version": "0.22.0",
|
||||
"description": "Core functionality that is shared across all Lion Web Components",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,76 @@
|
|||
# Change Log
|
||||
|
||||
## 0.15.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [d46b9894]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
- @lion/overlays@0.32.0
|
||||
|
||||
## 0.14.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/dialog",
|
||||
"version": "0.14.0",
|
||||
"version": "0.15.0",
|
||||
"description": "Show relative overlay content on click, as a webcomponent",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -37,8 +37,8 @@
|
|||
"./docs/styled-dialog-content.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/overlays": "^0.31.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/overlays": "^0.32.0"
|
||||
},
|
||||
"keywords": [
|
||||
"dialog",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,79 @@
|
|||
# Change Log
|
||||
|
||||
## 0.21.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.20.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/fieldset",
|
||||
"version": "0.20.0",
|
||||
"version": "0.21.0",
|
||||
"description": "Allows to groups multiple input fields or other fieldsets together",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -37,8 +37,8 @@
|
|||
"./docs/helpers/demo-fieldset-child.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0"
|
||||
},
|
||||
"keywords": [
|
||||
"fieldset",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,80 @@
|
|||
# Change Log
|
||||
|
||||
## 0.17.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- 7016a150: Validation: allow enums as outcome of a Validator
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
- f408f6f8: Updated the ValidateMixin \_\_setupValidators method to sync the calendar date with validator params with reference to this issue : https://github.com/ing-bank/lion/pull/1641/files#diff-bed9319548b16e509dd4a5c3d9c7c31175b577f91e433ee55a945e05339d2796R632
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- 9c1dfdcd: FormControl: allow a label-sr-only flag to provide visually hidden labels
|
||||
- 3772c943: form-core: expose 'mimicUserInput' test-helper
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.16.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/form-core",
|
||||
"version": "0.16.0",
|
||||
"version": "0.17.0",
|
||||
"description": "Form-core contains all essential building blocks for creating form fields and fieldsets",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -38,8 +38,8 @@
|
|||
"lion-validation-feedback.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/localize": "^0.23.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/localize": "^0.24.0"
|
||||
},
|
||||
"keywords": [
|
||||
"field",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,105 @@
|
|||
# Change Log
|
||||
|
||||
## 0.11.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [a64c552b]
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [f7df1ae8]
|
||||
- Updated dependencies [998d95f9]
|
||||
- Updated dependencies [1ea9f291]
|
||||
- Updated dependencies [85318e3b]
|
||||
- @lion/validate-messages@0.9.0
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/button@0.17.0
|
||||
- @lion/checkbox-group@0.20.0
|
||||
- @lion/combobox@0.10.0
|
||||
- @lion/fieldset@0.21.0
|
||||
- @lion/form@0.14.0
|
||||
- @lion/input@0.17.0
|
||||
- @lion/input-amount@0.16.0
|
||||
- @lion/input-date@0.14.0
|
||||
- @lion/input-datepicker@0.25.0
|
||||
- @lion/input-email@0.15.0
|
||||
- @lion/input-iban@0.18.0
|
||||
- @lion/input-range@0.12.0
|
||||
- @lion/input-stepper@0.8.0
|
||||
- @lion/listbox@0.13.0
|
||||
- @lion/localize@0.24.0
|
||||
- @lion/radio-group@0.20.0
|
||||
- @lion/select@0.16.0
|
||||
- @lion/select-rich@0.30.0
|
||||
- @lion/switch@0.20.0
|
||||
- @lion/textarea@0.15.0
|
||||
|
||||
## 0.10.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/form-integrations",
|
||||
"version": "0.10.0",
|
||||
"version": "0.11.0",
|
||||
"description": "The Form System allows you to create complex forms with various validation in an easy way",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -32,29 +32,29 @@
|
|||
"test": "cd ../../ && npm run test:browser -- --group form-integrations"
|
||||
},
|
||||
"dependencies": {
|
||||
"@lion/button": "^0.16.0",
|
||||
"@lion/checkbox-group": "^0.19.0",
|
||||
"@lion/combobox": "^0.9.0",
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/fieldset": "^0.20.0",
|
||||
"@lion/form": "^0.13.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0",
|
||||
"@lion/input-amount": "^0.15.0",
|
||||
"@lion/input-date": "^0.13.0",
|
||||
"@lion/input-datepicker": "^0.24.0",
|
||||
"@lion/input-email": "^0.14.0",
|
||||
"@lion/input-iban": "^0.17.0",
|
||||
"@lion/input-range": "^0.11.0",
|
||||
"@lion/input-stepper": "^0.7.0",
|
||||
"@lion/listbox": "^0.12.0",
|
||||
"@lion/localize": "^0.23.0",
|
||||
"@lion/radio-group": "^0.19.0",
|
||||
"@lion/select": "^0.15.0",
|
||||
"@lion/select-rich": "^0.29.0",
|
||||
"@lion/switch": "^0.19.0",
|
||||
"@lion/textarea": "^0.14.0",
|
||||
"@lion/validate-messages": "^0.8.0"
|
||||
"@lion/button": "^0.17.0",
|
||||
"@lion/checkbox-group": "^0.20.0",
|
||||
"@lion/combobox": "^0.10.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/fieldset": "^0.21.0",
|
||||
"@lion/form": "^0.14.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0",
|
||||
"@lion/input-amount": "^0.16.0",
|
||||
"@lion/input-date": "^0.14.0",
|
||||
"@lion/input-datepicker": "^0.25.0",
|
||||
"@lion/input-email": "^0.15.0",
|
||||
"@lion/input-iban": "^0.18.0",
|
||||
"@lion/input-range": "^0.12.0",
|
||||
"@lion/input-stepper": "^0.8.0",
|
||||
"@lion/listbox": "^0.13.0",
|
||||
"@lion/localize": "^0.24.0",
|
||||
"@lion/radio-group": "^0.20.0",
|
||||
"@lion/select": "^0.16.0",
|
||||
"@lion/select-rich": "^0.30.0",
|
||||
"@lion/switch": "^0.20.0",
|
||||
"@lion/textarea": "^0.15.0",
|
||||
"@lion/validate-messages": "^0.9.0"
|
||||
},
|
||||
"keywords": [
|
||||
"form",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,73 @@
|
|||
# Change Log
|
||||
|
||||
## 0.14.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/fieldset@0.21.0
|
||||
|
||||
## 0.13.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/form",
|
||||
"version": "0.13.0",
|
||||
"version": "0.14.0",
|
||||
"description": "It enhances the functionality of the native `form` component. It is designed to interact with (instances of) form fields",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,7 +36,7 @@
|
|||
"lion-form.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/fieldset": "^0.20.0"
|
||||
"@lion/fieldset": "^0.21.0"
|
||||
},
|
||||
"keywords": [
|
||||
"form",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,73 @@
|
|||
# Change Log
|
||||
|
||||
## 0.11.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.10.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/helpers",
|
||||
"version": "0.10.0",
|
||||
"version": "0.11.0",
|
||||
"description": "Helpers that are used throughout lion and can be used outside",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -35,7 +35,7 @@
|
|||
"sb-locale-switcher.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0"
|
||||
"@lion/core": "^0.22.0"
|
||||
},
|
||||
"keywords": [
|
||||
"action logger",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,74 @@
|
|||
# Change Log
|
||||
|
||||
## 0.15.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.14.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/icon",
|
||||
"version": "0.14.0",
|
||||
"version": "0.15.0",
|
||||
"description": "A web component easily displaying svg icons",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -37,7 +37,7 @@
|
|||
"./docs/icon-resolvers.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"singleton-manager": "^1.4.3"
|
||||
},
|
||||
"keywords": [
|
||||
|
|
|
|||
|
|
@ -1,5 +1,85 @@
|
|||
# Change Log
|
||||
|
||||
## 0.16.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [a64c552b]
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [f7df1ae8]
|
||||
- Updated dependencies [85318e3b]
|
||||
- @lion/validate-messages@0.9.0
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.15.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-amount",
|
||||
"version": "0.15.0",
|
||||
"version": "0.16.0",
|
||||
"description": "Provide a way for users to fill in an amount",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,11 +36,11 @@
|
|||
"lion-input-amount.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0",
|
||||
"@lion/localize": "^0.23.0",
|
||||
"@lion/validate-messages": "^0.8.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0",
|
||||
"@lion/localize": "^0.24.0",
|
||||
"@lion/validate-messages": "^0.9.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input-amount",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,85 @@
|
|||
# Change Log
|
||||
|
||||
## 0.14.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [a64c552b]
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [f7df1ae8]
|
||||
- Updated dependencies [85318e3b]
|
||||
- @lion/validate-messages@0.9.0
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.13.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-date",
|
||||
"version": "0.13.0",
|
||||
"version": "0.14.0",
|
||||
"description": "Provide a way for users to fill in a date",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,11 +36,11 @@
|
|||
"lion-input-date.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0",
|
||||
"@lion/localize": "^0.23.0",
|
||||
"@lion/validate-messages": "^0.8.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0",
|
||||
"@lion/localize": "^0.24.0",
|
||||
"@lion/validate-messages": "^0.9.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input-date",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,90 @@
|
|||
# Change Log
|
||||
|
||||
## 0.25.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
- 998d95f9: Added a fix by overriding the \_\_onValidatorUpdated() to sync the calendar dates when the validator params got changed
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [a64c552b]
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [d46b9894]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [f7df1ae8]
|
||||
- Updated dependencies [85318e3b]
|
||||
- @lion/validate-messages@0.9.0
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/calendar@0.19.0
|
||||
- @lion/input-date@0.14.0
|
||||
- @lion/localize@0.24.0
|
||||
- @lion/overlays@0.32.0
|
||||
|
||||
## 0.24.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-datepicker",
|
||||
"version": "0.24.0",
|
||||
"version": "0.25.0",
|
||||
"description": "Provide a way for users to fill in a date via a calendar overlay",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,13 +36,13 @@
|
|||
"lion-input-datepicker.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/calendar": "^0.18.0",
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input-date": "^0.13.0",
|
||||
"@lion/localize": "^0.23.0",
|
||||
"@lion/overlays": "^0.31.0",
|
||||
"@lion/validate-messages": "^0.8.0"
|
||||
"@lion/calendar": "^0.19.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input-date": "^0.14.0",
|
||||
"@lion/localize": "^0.24.0",
|
||||
"@lion/overlays": "^0.32.0",
|
||||
"@lion/validate-messages": "^0.9.0"
|
||||
},
|
||||
"keywords": [
|
||||
"calendar",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,85 @@
|
|||
# Change Log
|
||||
|
||||
## 0.15.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [a64c552b]
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [f7df1ae8]
|
||||
- Updated dependencies [85318e3b]
|
||||
- @lion/validate-messages@0.9.0
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.14.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-email",
|
||||
"version": "0.14.0",
|
||||
"version": "0.15.0",
|
||||
"description": "Provide a way for users to fill in an email",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,11 +36,11 @@
|
|||
"lion-input-email.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0",
|
||||
"@lion/localize": "^0.23.0",
|
||||
"@lion/validate-messages": "^0.8.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0",
|
||||
"@lion/localize": "^0.24.0",
|
||||
"@lion/validate-messages": "^0.9.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input-email",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,85 @@
|
|||
# Change Log
|
||||
|
||||
## 0.18.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [a64c552b]
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [f7df1ae8]
|
||||
- Updated dependencies [85318e3b]
|
||||
- @lion/validate-messages@0.9.0
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.17.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-iban",
|
||||
"version": "0.17.0",
|
||||
"version": "0.18.0",
|
||||
"description": "Provide a way for users to fill in an iban",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,11 +36,11 @@
|
|||
"lion-input-iban.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0",
|
||||
"@lion/localize": "^0.23.0",
|
||||
"@lion/validate-messages": "^0.8.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0",
|
||||
"@lion/localize": "^0.24.0",
|
||||
"@lion/validate-messages": "^0.9.0",
|
||||
"ibantools": "^2.2.0"
|
||||
},
|
||||
"keywords": [
|
||||
|
|
|
|||
|
|
@ -1,5 +1,76 @@
|
|||
# Change Log
|
||||
|
||||
## 0.12.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.11.1
|
||||
|
||||
### Patch Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-range",
|
||||
"version": "0.11.1",
|
||||
"version": "0.12.0",
|
||||
"description": "Provide a way for users to select one value from a range of values",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,9 +36,9 @@
|
|||
"lion-input-range.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.1",
|
||||
"@lion/input": "^0.16.0",
|
||||
"@lion/localize": "^0.23.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/input": "^0.17.0",
|
||||
"@lion/localize": "^0.24.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input-range",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,80 @@
|
|||
# Change Log
|
||||
|
||||
## 0.8.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
|
||||
## 0.7.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-stepper",
|
||||
"version": "0.7.0",
|
||||
"version": "0.8.0",
|
||||
"description": "This component enables the user to increase and decrease a numeric value by predefined range.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,9 +36,9 @@
|
|||
"lion-input-stepper.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input",
|
||||
|
|
|
|||
72
packages/input-tel-dropdown/CHANGELOG.md
Normal file
72
packages/input-tel-dropdown/CHANGELOG.md
Normal file
|
|
@ -0,0 +1,72 @@
|
|||
# @lion/input-tel-dropdown
|
||||
|
||||
## 0.1.0
|
||||
### Minor Changes
|
||||
|
||||
- 32b322c3: New component LionInpuTelDropdown
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [a882c94f]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
- @lion/localize@0.24.0
|
||||
- @lion/input-tel@0.1.0
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-tel-dropdown",
|
||||
"version": "0.0.0",
|
||||
"version": "0.1.0",
|
||||
"description": "Input field for entering phone numbers with the help of a dropdown region list",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -34,9 +34,9 @@
|
|||
"lion-input-tel-dropdown.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "0.21.1",
|
||||
"@lion/input-tel": "0.0.0",
|
||||
"@lion/localize": "0.23.0"
|
||||
"@lion/core": "0.22.0",
|
||||
"@lion/input-tel": "0.1.0",
|
||||
"@lion/localize": "0.24.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input",
|
||||
|
|
|
|||
76
packages/input-tel/CHANGELOG.md
Normal file
76
packages/input-tel/CHANGELOG.md
Normal file
|
|
@ -0,0 +1,76 @@
|
|||
# @lion/input-tel
|
||||
|
||||
## 0.1.0
|
||||
### Minor Changes
|
||||
|
||||
- a882c94f: New component "LionInputTel"
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
- @lion/localize@0.24.0
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input-tel",
|
||||
"version": "0.0.0",
|
||||
"version": "0.1.0",
|
||||
"description": "Input field for entering phone numbers, including validation, formatting and mobile keyboard support.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -37,10 +37,10 @@
|
|||
"lion-input-tel.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "0.21.1",
|
||||
"@lion/form-core": "0.16.0",
|
||||
"@lion/input": "0.16.0",
|
||||
"@lion/localize": "0.23.0"
|
||||
"@lion/core": "0.22.0",
|
||||
"@lion/form-core": "0.17.0",
|
||||
"@lion/input": "0.17.0",
|
||||
"@lion/localize": "0.24.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,77 @@
|
|||
# Change Log
|
||||
|
||||
## 0.17.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
|
||||
## 0.16.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/input",
|
||||
"version": "0.16.0",
|
||||
"version": "0.17.0",
|
||||
"description": "It enhances the functionality of the native `<input>` element",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,7 +36,7 @@
|
|||
"lion-input.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/form-core": "^0.16.0"
|
||||
"@lion/form-core": "^0.17.0"
|
||||
},
|
||||
"keywords": [
|
||||
"input",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,80 @@
|
|||
# @lion/listbox
|
||||
|
||||
## 0.13.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- 1ea9f291: Fix: Prevent default behavior while scrolling using arrow keys in a horizontal listbox
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.12.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/listbox",
|
||||
"version": "0.12.0",
|
||||
"version": "0.13.0",
|
||||
"description": "A listbox widget presents a list of options and allows a user to select one or more of them",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -39,8 +39,8 @@
|
|||
"lion-options.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0"
|
||||
},
|
||||
"keywords": [
|
||||
"form",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,74 @@
|
|||
# Change Log
|
||||
|
||||
## 0.24.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.23.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/localize",
|
||||
"version": "0.23.0",
|
||||
"version": "0.24.0",
|
||||
"description": "The localization system helps to manage localization data split into locales and automate its loading",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -34,7 +34,7 @@
|
|||
"sideEffects": false,
|
||||
"dependencies": {
|
||||
"@bundled-es-modules/message-format": "6.0.4",
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"singleton-manager": "^1.4.3"
|
||||
},
|
||||
"keywords": [
|
||||
|
|
|
|||
|
|
@ -1,5 +1,75 @@
|
|||
# Change Log
|
||||
|
||||
## 0.32.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- d46b9894: Fix check for css typed object support
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.31.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/overlays",
|
||||
"version": "0.31.0",
|
||||
"version": "0.32.0",
|
||||
"description": "Overlays System using lit-html for rendering",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -37,7 +37,7 @@
|
|||
"./docs/applyDemoOverlayStyles.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"@popperjs/core": "^2.5.4",
|
||||
"singleton-manager": "^1.4.3"
|
||||
},
|
||||
|
|
|
|||
|
|
@ -1,5 +1,75 @@
|
|||
# Change Log
|
||||
|
||||
## 0.8.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.7.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/pagination",
|
||||
"version": "0.7.0",
|
||||
"version": "0.8.0",
|
||||
"description": "A component that handles pagination.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,8 +36,8 @@
|
|||
"lion-pagination.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/localize": "^0.23.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/localize": "^0.24.0"
|
||||
},
|
||||
"keywords": [
|
||||
"lion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,75 @@
|
|||
# @lion/progress-indicator
|
||||
|
||||
## 0.8.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
- @lion/localize@0.24.0
|
||||
|
||||
## 0.7.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/progress-indicator",
|
||||
"version": "0.7.0",
|
||||
"version": "0.8.0",
|
||||
"description": "A progress indicator that is easily styleable and accessible in all contexts",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,8 +36,8 @@
|
|||
"lion-progress-indicator.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/localize": "^0.23.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/localize": "^0.24.0"
|
||||
},
|
||||
"keywords": [
|
||||
"lion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,80 @@
|
|||
# Change Log
|
||||
|
||||
## 0.20.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/input@0.17.0
|
||||
|
||||
## 0.19.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/radio-group",
|
||||
"version": "0.19.0",
|
||||
"version": "0.20.0",
|
||||
"description": "Manage a group of choices",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -38,9 +38,9 @@
|
|||
"lion-radio-group.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/input": "^0.16.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/input": "^0.17.0"
|
||||
},
|
||||
"keywords": [
|
||||
"lion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,84 @@
|
|||
# Change Log
|
||||
|
||||
## 0.30.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [d46b9894]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- Updated dependencies [1ea9f291]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/button@0.17.0
|
||||
- @lion/listbox@0.13.0
|
||||
- @lion/overlays@0.32.0
|
||||
|
||||
## 0.29.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/select-rich",
|
||||
"version": "0.29.0",
|
||||
"version": "0.30.0",
|
||||
"description": "Provides a select with options that can contain html",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -40,11 +40,11 @@
|
|||
"lion-select-rich.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/button": "^0.16.0",
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/listbox": "^0.12.0",
|
||||
"@lion/overlays": "^0.31.0"
|
||||
"@lion/button": "^0.17.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/listbox": "^0.13.0",
|
||||
"@lion/overlays": "^0.32.0"
|
||||
},
|
||||
"keywords": [
|
||||
"field",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,79 @@
|
|||
# Change Log
|
||||
|
||||
## 0.16.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.15.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/select",
|
||||
"version": "0.15.0",
|
||||
"version": "0.16.0",
|
||||
"description": "Provide a set of options where you can select one",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,8 +36,8 @@
|
|||
"lion-select.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0"
|
||||
},
|
||||
"keywords": [
|
||||
"lion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,74 @@
|
|||
# Change Log
|
||||
|
||||
## 0.11.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.10.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/steps",
|
||||
"version": "0.10.0",
|
||||
"version": "0.11.0",
|
||||
"description": "Breaks a single goal down into dependable sub-tasks.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -38,7 +38,7 @@
|
|||
"lion-steps.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0"
|
||||
"@lion/core": "^0.22.0"
|
||||
},
|
||||
"keywords": [
|
||||
"lion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,80 @@
|
|||
# Change Log
|
||||
|
||||
## 0.20.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
- @lion/helpers@0.11.0
|
||||
|
||||
## 0.19.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/switch",
|
||||
"version": "0.19.0",
|
||||
"version": "0.20.0",
|
||||
"description": "A Switch is used for switching a property or feature on and off",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -38,9 +38,9 @@
|
|||
"lion-switch-button.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/helpers": "^0.10.0"
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@lion/helpers": "^0.11.0"
|
||||
},
|
||||
"keywords": [
|
||||
"lion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,75 @@
|
|||
# Change Log
|
||||
|
||||
## 0.12.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- 03c294c9: tabs: allow to be initialized withhout children
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.11.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/tabs",
|
||||
"version": "0.11.0",
|
||||
"version": "0.12.0",
|
||||
"description": "Allows users to quickly move between a small number of equally important views.",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,7 +36,7 @@
|
|||
"lion-tabs.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0"
|
||||
"@lion/core": "^0.22.0"
|
||||
},
|
||||
"keywords": [
|
||||
"lion",
|
||||
|
|
|
|||
|
|
@ -1,5 +1,79 @@
|
|||
# Change Log
|
||||
|
||||
## 0.15.0
|
||||
|
||||
### Minor Changes
|
||||
|
||||
- 672c8e99: New documentation structure
|
||||
- aa8b8916: BREAKING CHANGE: Work without polyfill if possible
|
||||
|
||||
When using [component composition](https://lit.dev/docs/composition/component-composition/) in a Lion Component we always made it very explicit which sub-components are used.
|
||||
On top of that we scoped these [sub components](https://open-wc.org/docs/development/scoped-elements/) to the [current shadow root](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) allowing multiple version to be used simultaneously.
|
||||
|
||||
To enable this features we relied on the fact that the `ScopedElementsMixin` did loaded the needed polyfill for us.
|
||||
|
||||
We however over time got feedback from multiple consumers that lion components "break the app as soon as you load them".
|
||||
The reasons is/was that not everyone is always using `ScopedElementsMixin` or in full control of the app (or its load order).
|
||||
|
||||
To quote the release notes of `ScopedElementsMixin` v2.1.0:
|
||||
|
||||
> ScopedElementsMixin 2.x tried to be as convenient as possible by automatically loading the scoped custom elements registry polyfill.
|
||||
> This however led to a fatal error whenever you registered any component before ScopedElementsMixin was used.
|
||||
|
||||
And this was the case.
|
||||
|
||||
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
|
||||
|
||||
This essentially means the polyfill became optional which results in the following behavior
|
||||
|
||||
1. If polyfill is not loaded it will use the global registry as a fallback
|
||||
2. Log error if actually scoping is needed and polyfill is not loaded
|
||||
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
|
||||
|
||||
```diff
|
||||
- const myButton = this.shadowRoot.createElement('my-button');
|
||||
+ const myButton = this.createScopedElement('my-button');
|
||||
```
|
||||
|
||||
This also removes `@webcomponents/scoped-custom-element-registry` as a production dependency.
|
||||
|
||||
If you need scoping be sure to load the polyfill before any other web component gets registered.
|
||||
|
||||
It may look something like this in your HTML
|
||||
|
||||
```html
|
||||
<script src="/node_modules/@webcomponents/scoped-custom-element-registry/scoped-custom-element-registry.min.js"></script>
|
||||
```
|
||||
|
||||
or if you have an SPA you can load it at the top of your app shell code
|
||||
|
||||
```js
|
||||
import '@webcomponents/scoped-custom-element-registry';
|
||||
```
|
||||
|
||||
You need scoping if you want to
|
||||
|
||||
use 2 major versions of a web component (e.g. in an SPA pageA uses 1.x and pageB uses 2.x of color-picker)
|
||||
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
|
||||
|
||||
See more details at
|
||||
|
||||
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
|
||||
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
|
||||
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- Updated dependencies [9c1dfdcd]
|
||||
- Updated dependencies [3772c943]
|
||||
- Updated dependencies [66531e3c]
|
||||
- Updated dependencies [672c8e99]
|
||||
- Updated dependencies [7016a150]
|
||||
- Updated dependencies [aa8b8916]
|
||||
- Updated dependencies [f408f6f8]
|
||||
- @lion/form-core@0.17.0
|
||||
- @lion/core@0.22.0
|
||||
|
||||
## 0.14.0
|
||||
|
||||
### Minor Changes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lion/textarea",
|
||||
"version": "0.14.0",
|
||||
"version": "0.15.0",
|
||||
"description": "Provide a way for users to write text that is multiple lines long",
|
||||
"license": "MIT",
|
||||
"author": "ing-bank",
|
||||
|
|
@ -36,8 +36,8 @@
|
|||
"lion-textarea.js"
|
||||
],
|
||||
"dependencies": {
|
||||
"@lion/core": "^0.21.0",
|
||||
"@lion/form-core": "^0.16.0",
|
||||
"@lion/core": "^0.22.0",
|
||||
"@lion/form-core": "^0.17.0",
|
||||
"@types/autosize": "^3.0.7",
|
||||
"autosize": "4.0.2"
|
||||
},
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue