@sap/ux-specification 1.100.4 → 1.102.2

package/CHANGELOG.md

@@ -4,112 +4,76 @@ All notable changes to this project are documented in this file.
 
 This project adheres to [Semantic Versioning](http://semver.org/) and the changelog is formatted based on [Keep a Changelog](http://keepachangelog.com/).
 
-## [1.100.4] - 2022-06-02
+## [1.102.2] - 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
 
+- OData V4:
+
 ### Deprecated
 
 ### Fixed
-OData V4:
-- If `defaultAnnotationPath` is used, corresponding custom columns were not considered on list report page.
-
-### Quality
-Upgrade node & node-version to 14.x
-
-## [1.100.3] - 2022-05-19
 
-### Changed
-- OData V4: 
-    - For list report views, the content of title and description in the schema got exchanged.
-    - Custom columns having an invalid anchor are not filtered out anymore but added to the schema (at the end of the columns' list). This better supports fixing the situation and is necessary so that the import fills the properties correctly.
-    - LR: If views are enabled, generic table columns won't be used/filled.
+- OData V2:
+  - OVP:
 
+- 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
 
-### Fixed
-- 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.
-    - In case of multiple custom columns with an invalid anchor the app schema generation ran into an endless loop.
-    - 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.
-    - Tag 'hidden' was added to the property annotationPath of the ALP chart view in app schema.
-    - 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.100.2] - 2022-05-05
+- Switch from nexus repository to artifactory
+
+## [1.102.1] - 2022-06-29
 
 ### Added
-- OData V4: 
-  - The title of ALP or List Report views is now following the same criteria as the UI5 run-time.
+
+- OData V4:
+  - Extend pagemap support for freestyle apps using FPM library
 
 ### Fixed
-- OData V4:  
-  - Problems with deletion of ListReport table views.
-  - Unknown properties removed from custom section definition in 'manifest.json'.
-  - delete 'table/personalization' object property in 'manifest.json' if last property was removed.
-  - Export. Delete of entries from `table/views` - views were not deleted during export if entries in annotation file were deleted as first.
-  - When changing the table type in the page editor for LRP (V4), the respective manifest setting is not updated as long as this page is configured with the primary and secondary views
-- 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.
 
-### Quality
-- Switch consumption of "@sapui5/ts-types" to "@sapui5/ts-types-esm".
+- 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.100.1] - 2022-04-21
+## [1.102.0] - 2022-06-16
 
 ### Added
 
-- 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. 
-- OData V4:
-  - OP: Added support for presentationVariants with chart or lineItem visualization
+- Missing exposure of type definitions was added.
 
-- Documentation actualized with regards to the new release version 1.100.
+### Changed
 
-### Fixed
-- 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. 
-  - 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.
+OData V2:
 
-### Quality
-- upgrade ejs to 3.1.7
-- SonarQube: issued solved with regards to cognitive complexity
-- upgrade ejs to 3.1.7
+- Custom column property "columnIndex". Schema enhancement by defining range using "minimum=0".
 
-## [1.100.0] - 2022-04-07
+### Removed
 
-### Added
+OData V4:
 
-- OData V2:
-  - LR: Added support for `multiEdit` property to enable mass edit feature.
-- OData V4:
-  - LR: Added support for property `hideFilterBar`
-  - Support of defaultTemplateAnnotationPath as property; consider defaultTemplateAnnotationPath when retrieving the relevant table settings and while switching to ALP flavour.
+- In case of List Report views, non-applicable table properties are removed.
 
 ### Fixed
 
-- OData V2:
-  - Extensions - empty "extensions" object was created in "sap.ui5/"extends"/"extensions"/"sap.ui.viewExtensions"/"sap.suite.ui.generic.template.ListReport.view.ListReport".
-
-### Quality
+OData V4:
 
-- Replace type object for schemas by Definition from 'typescript-json-schema'.
-- Upgrade of async.
+- In case of List Report views, custom columns with navigation property are considered for the correct view.
+- Avoid creation of empty personalization object
+OData V2:
+- Custom column issue with Grid/Tree/Analytical table types - empty second custom column is added in xml files