@sap/ux-specification 1.84.41 → 1.84.44

package/CHANGELOG.md

@@ -8,6 +8,56 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 *Official support of OData V4*
 
+## [1.84.44] - 2022-07-28
+
+### Added
+
+### Changed
+
+### Removed
+
+### Deprecated
+
+### Fixed
+
+### Quality
+
+- Upgrade of webpack and dependent modules
+- Upgrade of terser
+- Upgrade of glob-parent
+- Upgrade of lerna
+
+## [1.84.43] - 2022-07-14
+
+### Changed
+
+- OData V4: In case of PresentationVariant definitions for charts or line items, an intermediate node had originally been introduced in the Object Page schema that represents the PresentationVariant. This multi-level propagation of references caused issues in the consuming UI, thus the intermediate node got deleted again. The PresentationVariant must be determined by the consuming application if necessary.
+
+### Fixed
+
+- OData V4:
+  - Properties of custom columns on object page had not been exported correctly if the table is associated to another entity type via navigation path or is using a PresentationVariant.
+  The value help of the anchor in LSP (config JSON) also did not show the right values.
+  - Object Page: Fixed an issue with the schema that `annotationPath` for Object Page Table Sections did not contain `qualifier`;
+  wrong `annotationPath` and `isViewNode` settings are adjusted.
+  - Fixed an issue with export that multiple changes to view's `key` property created duplicated entries in manifest.json
+
+### Quality
+
+- Switch from nexus repository to artifactory
+
+## [1.84.42] - 2022-06-29
+
+### Fixed
+
+- OData V2:
+  - OVP: LSP for `model` property of a card now lists models from sap.ui5 section of manifest.json
+  - Table type property is now set to blank in case not maintained in manifest.json
+  - If two sections of object page referred to an element (e.g. action, table column) of the same name, they had been sync'd by the program logic: changes of one property had also been refelected in the other.
+  - One UI adaptation or flexibility change may have been shown multiple times in the config, at different sections.
+  - No sorting by time took place before for flexibility changes, as a result an older change of the same property may have shown up instead of the newer one.
+  - If several flexibility changes existed for the same control property, secondary ones had not been imported correctly: you could find them under a wrong property name in the config JSON file.
+
 ## [1.84.41] - 2022-06-16
 
 ### Added
@@ -15,7 +65,9 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 - Missing exposure of type definitions was added.
 
 ### Changed
+
 OData V2:
+
 - Custom column property "columnIndex". Schema enhancement by defining range using "minimum=0".
 
 ### Removed
@@ -24,16 +76,12 @@ OData V4:
 
 - In case of List Report views, non-applicable table properties are removed.
 
-### Deprecated
-
 ### Fixed
 
 OData V2:
 
 - Custom column issue with Grid/Tree/Analytical table types - empty second custom column is added in xml files
 
-### Quality
-
 ## [1.84.40] - 2022-06-02
 
 ### Added
@@ -49,12 +97,6 @@ OData V4:
 - Titles of charts in sections and header sections now correspond to the run-time.
 - Add "annotationPath" schema property to schema for "Table" definition in simple list report.
 
-### Removed
-
-### Deprecated
-
-### Fixed
-
 ### Quality
 
 Upgrade node & node-version to 14.x