@sap/ux-specification 1.90.9 → 1.90.13

package/CHANGELOG.md

@@ -4,25 +4,118 @@ 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.9] - 2021-09-08
+## [1.90.13] - 2021-10-20
 
 ### Added
 
+- OData V2:
+  - Support for (Sub)Section properties: `visible`.
+  - ALP: Schema now comprises of entity properties for config `createWithParameterDialog`->`fields`
+  - OP: Added support for multiple flex changes in Form and Header Actions
+- V2 & V4: Footer actions are now part of the schema. A node for header actions is visible even if there are no actions yet.
+
+### Changed
+
+- 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
+
+- OData V2:
+  - OVP: Removed `tab` property from `Stack` and `Link List` cards as view switch control is not supported
+
+### Deprecated
+
+### Fixed
+
 - OData V4:
-  - Header Facets are now shown in the schemas and configs, along with their actual manifest settings.
+  - 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: 
+  - 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.
+
+### Quality
+
+- Settings for sonarlint have been added.
+- Upgrade of Annotation Vocabularies Tools.
+- Fix of code smells reported by SonarQube.
+
+## [1.90.12] - 2021-10-18
+
+### Fixed
+
+For some V4 apps, the export of property changes failed due to invalid schema definitions.
+
+## [1.90.11] - 2021-10-06
+
+### Added
+
+- Annotation path com.sap.vocabularies.UI.v1.HeaderInfo added to ObjectPageHeader in V2 and V4.
+- Added `i18nClassification` for `title`, `description` properties for `App.json` schema in V2 and V4.
+- OData V4: Header actions are now part of the Object Page schema.
 - OData V2:
-  - OVP: Added support for property `dataPointAnnotationPath` in ListCard settings
-  - OVP: Added support for OData V4 Link List Card
+  - OVP: Added support for property `annotationPath` in Linklist card settings.
+  - OVP: property `requireAppAuthorization` is now supported for all card types.
+
+### Changed
+
+- README file updated.
+- Order and naming of view nodes for the V2 Object Page adapted.
+- Pattern for binding changes in V2: there are now two different patterns for List Report and Object Page; the one for the Object Page  provides the additional enum values  "{ui>/editable}" and "{= !${ui>/editable}}"
+
+### Fixed
+
+- V4: if one section comprises a field group without qualifier, and one referred to UI.Identification, the properties of the field group had been displayed for Identification section of header facet as well.
+
+### Quality
+
+- Fix of vulnerabilities by upgrade of npm modules.
+- Fix of bugs nd code smells reported by SonarQube.
+
+## [1.90.10] - 2021-09-22
+
+### Added
+
+- 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.
 
 ### Changed
 
+- The default for titles and labels of schema nodes - in case of missing annotation labels - has been adapted, for facets and header facets. There will be node-specific content now in all cases instead of generic defaults like "Form".
+
 ### Removed
 
 ### Deprecated
 
 ### Fixed
 
-- V4. Import and export of Custom Page properties could get out of sync when specific properties were missing.  
+- 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
+
+### Quality
+
+- Bugs & code smells removed that had been detected by SonarQube
+
+## [1.90.9] - 2021-09-08
+
+### Added
+
+- OData V4:
+  - Header Facets are now shown in the schemas and configs, along with their actual manifest settings.
+- OData V2:
+  - OVP: Added support for property `dataPointAnnotationPath` in ListCard settings
+  - OVP: Added support for OData V4 Link List Card
+
+### Fixed
+
+- OData V4: Import and export of Custom Page properties could get out of sync when specific properties were missing.  
 
 ## [1.90.8] - 2021-08-25
 
@@ -37,11 +130,7 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 ### Changed
 
-- V2. Unresolvable facets are not returned by schema to avoid creation of corrupted custom sections 
-
-### Removed
-
-### Deprecated
+- OData V2: Unresolvable facets are not returned by schema to avoid creation of corrupted custom sections 
 
 ### Fixed
 
@@ -77,10 +166,6 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 - The generic schemas now already comprise anyOf definitions for enums of type string that allow binding changes. Previously this was only added during the generation of app specific schemas.
 
-### Removed
-
-### Deprecated
-
 ### Fixed
 
 - A common function was introduced to resolve path references of Common.Label annotations; endless loop references are interjected, the variable value or key is returned in this case.
@@ -99,12 +184,6 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 - OData V2: dateSettings property of Filterbar now supports addtional values
 - OData V2: Added growingThreshold property to Responsive Tables
 
-### Changed
-
-### Removed
-
-### Deprecated
-
 ### Fixed
 
 - When starting the app modeler for certain CDS projects, an exception occurs, and no pages nor schemas are listed.
@@ -124,10 +203,6 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 - The import functions for filling the content of config files are now instantiating the required metadata based on factory classes (that had been introduced for the export before).
 
-### Removed
-
-### Deprecated
-
 ### Fixed
 
 - In the annotationPath of columns, qualifiers had not been added.

package/README.md

@@ -3,10 +3,10 @@
 This package specifies the structure of SAP Fiori Element templates in form of typescript types and JSON schema files. You can find the JSON schemas under dist/schema.
 It is used by SAP Fiori Tools (see documentation link below) but can also be used independent from this application.
 
-The major and minor version of this specification package matches the major and minor version of SAP UI5, which contains Fiori elements.
+The major and minor version of this specification package matches the major and minor version of SAPUI5, which contains Fiori elements.
 
 _Example_:  
-`@sap/ux-specification@1.76.x` specifies the Fiori elements that are delivered with UI5 version 1.76.x
+`@sap/ux-specification@1.76.x` specifies the Fiori elements that are delivered with SAPUI5 version 1.76.x
 
 The module supports both the OData V2 and the OData V4 version of the templates (aka FioriElementsVersion), you thus can find two different access points for the typescript definitions:
 
@@ -24,8 +24,8 @@ You can retrieve any generic schema via schemaAccess.ts.
 Besides the specification, src/api.ts provides functions that can be used with SAP Fiori apps in connection with the JSON schemas:
 
 - generateSchema: converts one generic schema to an application specific one, enriched by app specific information like annotations.
-- importConfig: imports information from the app, like manifest settings or UI5 flexibility changes, into one JSON configuration file that relates to a given schema (representing the central settings of the app or of a page of the app).
-- exportConfig: exports from one JSON configuration file, returning an updated manifest.json file and a list of UI5 flexibility changes.
+- importConfig: imports information from the app, like manifest settings or SAPUI5 flexibility changes, into one JSON configuration file that relates to a given schema (representing the central settings of the app or of a page of the app).
+- exportConfig: exports from one JSON configuration file, returning an updated manifest.json file and a list of SAPUI5 flexibility changes.
 - importProject: imports information from the app and generates all schemas and JSON configuration files.
 - importProjectSchema: imports information from the app and generates all schemas but no JSON configuration files.
 - getApiVersion: returns the given API version. The API version starts with 1 and will only be increased in case of incompatible changes where the consumption layer must react on.