From fc55726a97c8e55dfa88676416053295b167f06e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 9 Dec 2022 15:24:53 +0000 Subject: [PATCH] Version Packages --- .changeset/modern-oranges-roll.md | 5 ----- .changeset/twelve-snakes-wait.md | 28 --------------------------- .changeset/twenty-pigs-peel.md | 5 ----- packages/ui/CHANGELOG.md | 32 +++++++++++++++++++++++++++++++ packages/ui/package.json | 2 +- 5 files changed, 33 insertions(+), 39 deletions(-) delete mode 100644 .changeset/modern-oranges-roll.md delete mode 100644 .changeset/twelve-snakes-wait.md delete mode 100644 .changeset/twenty-pigs-peel.md diff --git a/.changeset/modern-oranges-roll.md b/.changeset/modern-oranges-roll.md deleted file mode 100644 index f8cc101bc..000000000 --- a/.changeset/modern-oranges-roll.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@lion/ui': patch ---- - -datepicker uses no calender-overlay-frame element anymore diff --git a/.changeset/twelve-snakes-wait.md b/.changeset/twelve-snakes-wait.md deleted file mode 100644 index 5ab79c707..000000000 --- a/.changeset/twelve-snakes-wait.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -'@lion/ui': patch ---- - -Overlay System uses `` for top layer functionality of all overlays. -This means overlays positioned relative to viewport won't be moved to the body. - -This has many benefits for the App Developer: - -- "context" will be kept: - - css variables and parts/theme will work - - events work without the need for "repropagation" (from body to original context) - - accessibility relations between overlay content and its context do not get lost -- initial renderings become more predictable (since we don't need multiple initializations on multiple connectedCallbacks) -- performance: less initialization, thus better performance -- maintainability: handling all edge cases involved in moving an overlay to the body grew out of hand -- developer experience: - - no extra container components like overlay-frame/calendar-frame needed that maintain styles - - adding a contentWrapperNode is not needed anymore - -There could be small differences in timings though (usually we're done rendering quicker now). -Code that relies on side effects could be affected. Like: - -- the existence of a global Root node) -- the fact that global styles would reach a dialog placed in the body - -For most users using either OverlayController, OverlayMixin or an element that uses OverlayMixin (like LionInputDatepicker, LionRichSelect etc. etc.) -nothing will change in the public api. diff --git a/.changeset/twenty-pigs-peel.md b/.changeset/twenty-pigs-peel.md deleted file mode 100644 index 86c702de3..000000000 --- a/.changeset/twenty-pigs-peel.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@lion/ui': patch ---- - -depend on @popperjs/core diff --git a/packages/ui/CHANGELOG.md b/packages/ui/CHANGELOG.md index 8d945de6f..5173a2d7b 100644 --- a/packages/ui/CHANGELOG.md +++ b/packages/ui/CHANGELOG.md @@ -1,5 +1,37 @@ # @lion/ui +## 0.0.10 + +### Patch Changes + +- 36910e5d: datepicker uses no calender-overlay-frame element anymore +- 64c0e26c: Overlay System uses `` for top layer functionality of all overlays. + This means overlays positioned relative to viewport won't be moved to the body. + + This has many benefits for the App Developer: + + - "context" will be kept: + - css variables and parts/theme will work + - events work without the need for "repropagation" (from body to original context) + - accessibility relations between overlay content and its context do not get lost + - initial renderings become more predictable (since we don't need multiple initializations on multiple connectedCallbacks) + - performance: less initialization, thus better performance + - maintainability: handling all edge cases involved in moving an overlay to the body grew out of hand + - developer experience: + - no extra container components like overlay-frame/calendar-frame needed that maintain styles + - adding a contentWrapperNode is not needed anymore + + There could be small differences in timings though (usually we're done rendering quicker now). + Code that relies on side effects could be affected. Like: + + - the existence of a global Root node) + - the fact that global styles would reach a dialog placed in the body + + For most users using either OverlayController, OverlayMixin or an element that uses OverlayMixin (like LionInputDatepicker, LionRichSelect etc. etc.) + nothing will change in the public api. + +- 00063d73: depend on @popperjs/core + ## 0.0.9 ### Patch Changes diff --git a/packages/ui/package.json b/packages/ui/package.json index 1c2e87a4a..bfaf5904b 100644 --- a/packages/ui/package.json +++ b/packages/ui/package.json @@ -1,6 +1,6 @@ { "name": "@lion/ui", - "version": "0.0.9", + "version": "0.0.10", "description": "A package of extendable web components", "license": "MIT", "author": "ing-bank",