@sap/ux-specification 1.90.13 → 1.90.17

package/CHANGELOG.md

@@ -4,6 +4,93 @@ 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.90.17] - 2022-01-12
+
+### Added
+
+- OData V2:
+  - OP: properties of footer actions are displayed and supported in side panel
+  - properties of toolbar actions are displayed and supported in side panel
+  - OVP: The property `showLineItemDetail` is now supported for List and Table cards
+  - OP: Schema now supports column extensions for TreeTable
+
+### Changed
+
+- OData V2:
+  - property `filterDefaultsFromSelectionVariant` is now only supported for AnalyticalListPage floorplan
+  - OVP: The property `tabs` and `addOdataSelect` can now be confirued for all cards
+- OData V4:
+  - property `afterExecution` of table columns now is only visible for actions but not for other record types
+  - deprecated `name` property and support new `template` property for custom sections in manifest
+
+### Removed
+
+- OData V2:
+  - OVP: removed `tabs` property from card level
+
+### Deprecated
+
+### Fixed
+
+- OData V2:
+  - correct schema generation in case multiple facets are referring to lineitem annotation of same entity
+  - Facet Id is considered for import and export of manifest settings
+  - Fixed sync issues in case no text is provided for custom columns
+- OData V4:
+  - Avoid exporting empty arrays to manifest.json
+
+### Quality
+
+- Upgrade of trim-off-newlines
+- Upgrade of yarn classic
+- New whitesource endpoint
+- Upgrade of follow-redirects
+
+## [1.90.16] - 2021-12-01
+
+### Added
+
+- Added enum support for `annotationPath` as part of quick variant selection or views
+- Property entitySet added to V4 views; enum support for entitySet of multiple views in V2 and V4
+- OData V2:
+  - LR: Added support for `annotationPath` property to allow setting default filter values
+
+### Fixed
+
+- Schemas and configs are now generated for applications without annotations
+- OData V4:
+  - Properties of (Header)Sections with missing facet Id are no longer displayed in properties panel
+  - export of deletion of object page columns did no work
+
+### Quality
+
+- New build version `build:dev` without generation of documentation html
+- Fixed an issue with missing `log` function after webpack
+
+## [1.90.15] - 2021-11-17
+
+### Added
+
+- OData V4: Enhance schema with `dataType`, `annotationPath` information for display on columns, fields and selection fields in Page editor
+
+### Fixed
+
+- Invalid references in generated schemas have been fixed.
+
+### Quality
+
+- Use of "@sapui5/ts-types": "1.90.9", replacement of own type definitions in case of suitable sapui5 type.
+
+## [1.90.14] - 2021-11-03
+
+### Changed
+
+- In the JSON schema, the description of DataPoints as part of sections or header facets now reflects the Title of the target annotation.
+
+### Quality
+
+- Code smell solved: "Define a constant instead of duplicating this literal n times."
+
 ## [1.90.13] - 2021-10-20
 
 ### Added
@@ -16,7 +103,7 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 ### Changed
 
-- OData V2: 
+- OData V2:
   - Enhanced sync logic to use generic approach for handling unknown properties. As a result sync logic is more robust and handles more unknown properties.
 
 ### Removed
@@ -31,7 +118,7 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 - OData V4:
   - Pages Schema. Exception if path in UI.SelectionFields is not valid.
   - Object page sections referring to UI.Identification with qualifer shall show actions besides the fields.
-- V2 & V4: 
+- V2 & V4:
   - replace alias of namespace definitions of header actions even for references that are not related to OData vocabularies.
   - Add `visible` property to DataField types
 - annotationPath definitions of header and footer actions.
@@ -80,8 +167,8 @@ For some V4 apps, the export of property changes failed due to invalid schema de
 
 - New html files showing a graphical representation of the content of each generic schema.
 - OData V2:
-    - We show field groups and fields now as part of the object page schema, and allow the maintenance of the visible property for fields.
-    - Support of property `flexEnabled`on app level.
+  - We show field groups and fields now as part of the object page schema, and allow the maintenance of the visible property for fields.
+  - Support of property `flexEnabled`on app level.
 
 ### Changed
 
@@ -93,11 +180,11 @@ For some V4 apps, the export of property changes failed due to invalid schema de
 
 ### Fixed
 
-- OData V2: 
-    - Invalid flexChanges are now ignored during sync, hence configs and pages files are created.
+- OData V2:
+  - Invalid flexChanges are now ignored during sync, hence configs and pages files are created.
 - OData V4:
-    - Exception occurred in case of invalid custom page definitions in manifest
-    - Page determination went wrong in case of irregular ordering of routing targets
+  - Exception occurred in case of invalid custom page definitions in manifest
+  - Page determination went wrong in case of irregular ordering of routing targets
 
 ### Quality
 
@@ -130,7 +217,7 @@ For some V4 apps, the export of property changes failed due to invalid schema de
 
 ### Changed
 
-- OData V2: Unresolvable facets are not returned by schema to avoid creation of corrupted custom sections 
+- OData V2: Unresolvable facets are not returned by schema to avoid creation of corrupted custom sections
 
 ### Fixed