@sap/ux-specification 1.84.40 → 1.84.43

package/CHANGELOG.md

@@ -8,16 +8,13 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 *Official support of OData V4*
 
-## [1.84.40] - 2022-06-02
+## [1.84.43] - 2022-07-14
 
 ### Added
-OData V4:
-- In case of a default (without qualifier) Selection-/PresentationVariant, the table settings and columns are now considered on list report page.
 
 ### Changed
-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.
+
+- 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.
 
 ### Removed
 
@@ -25,19 +22,85 @@ OData V4:
 
 ### Fixed
 
+- OData V2:
+
+- 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
-Upgrade node & node-version to 14.x
 
+- 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
+
+- Missing exposure of type definitions was added.
+
+### Changed
+
+OData V2:
+
+- Custom column property "columnIndex". Schema enhancement by defining range using "minimum=0".
+
+### Removed
+
+OData V4:
+
+- In case of List Report views, non-applicable table properties are removed.
+
+### Fixed
+
+OData V2:
+
+- Custom column issue with Grid/Tree/Analytical table types - empty second custom column is added in xml files
+
+## [1.84.40] - 2022-06-02
+
+### Added
+
+OData V4:
+
+- In case of a default (without qualifier) Selection-/PresentationVariant, the table settings and columns are now considered on list report page.
+
+### Changed
+
+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.
+
+### Quality
+
+Upgrade node & node-version to 14.x
 
 ## [1.84.39] - 2022-05-19
 
 ### Changed
-- OData V4: 
-    - For list report views, the content of title and description in the schema got exchanged.
-    - LR: If views are enabled, generic table columns won't be used/filled.
+
+- OData V4:
+  - For list report views, the content of title and description in the schema got exchanged.
+  - LR: If views are enabled, generic table columns won't be used/filled.
 
 ### Fixed
-- OData V4: 
+
+- OData V4:
   - If the table setting creationMode existed in the outdated string format, the export just had overwritten the string. Now, an implicit conversion to the new object format takes place.
   - No import of property annotationPath was happening at chart views of List Report.
   - In the app specific schema, the description was missing for charts in sections.
@@ -45,16 +108,20 @@ Upgrade node & node-version to 14.x
   - If defaultTemplateAnnotationPath is maintained and refers to an annotation other than UI.LineItem, the table settings and columns of the referred definition are now imported correctly.
 
 ### Quality
+
 - Code smells fixed, as reported by sonarQube.
 - Upgrade of annotation vocabularies tools.
 
 ## [1.84.38] - 2022-05-05
 
 ### Added
-OData V4: 
+
+OData V4:
+
 - The title of ALP or List Report views is now following the same criteria than the UI5 run-time.
 
 ### Fixed
+
 - OData V4:  
   - Problems with deletion of ListReport table views.
   - Unknown properties removed from custom section definition in 'manifest.json'.
@@ -63,30 +130,32 @@ OData V4:
 
 - OData V2:
   - Sections and subsections with a reference to Communication.Contact or Communication.Address had not been shown, support of flexibility changes for them.
-  - Facet or section references with multi-level navigation had not been handled correctly. 
+  - Facet or section references with multi-level navigation had not been handled correctly.
 
 ## [1.84.37] - 2022-04-21
 
 ### Added
+
 - Documentation actualised with regards to the new release version 1.100.
 
 - OData V2:
   - LR: Old settings for table type (tableType) had been ignored in newer specification releases. As a consequence, you may have found the table type twice in manifest, once with the old syntax and an additional entry with the new syntax, after switching to a newer UI5 version.
-  Now an implicit conversion to the new tableSettings takes place, and the old setting gets automatically replaced during the export. 
+  Now an implicit conversion to the new tableSettings takes place, and the old setting gets automatically replaced during the export.
 - OData V4:
   - OP: Added support for presentation variants with chart or table visualization
 
 ### Fixed
 
-- OData V4: 
+- OData V4:
   - Exception in case of multi-tab views in manifest that referred to a SelectionVariant.
-  - Export of table settings of list report was targeting the wrong manifest settings if a defaultTemplateAnnotationPath is defined, pointing to a SelectionPresentationVariant. 
+  - Export of table settings of list report was targeting the wrong manifest settings if a defaultTemplateAnnotationPath is defined, pointing to a SelectionPresentationVariant.
   - List report with multiple views: insert and reordering was not supported correctly.
 - OData V2:
   - After an entry of quickVariantSelectionX got deleted, the entry still was present in manifest.json.  
   - Sections of subordinate object pages had not been added correctly to the app schema in all cases.
 
 ### Quality
+
 - upgrade ejs to 3.1.7
 - SonarQube: issued solved with regards to cognitive complexity