@sap/ux-specification 1.71.41 → 1.71.45

package/CHANGELOG.md

@@ -4,17 +4,17 @@ 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.71.41] - 2021-09-xx
+## [1.71.45] - 2021-11-03
 
 ### 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
+
 
 ### 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.
+- In the JSON schema, the description of DataPoints as part of sections or header facets now reflects the Title of the target annotation.
+
 ### Removed
 
 ### Deprecated
@@ -23,6 +23,88 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 ### Quality
 
+- Code smell solved: "Define a constant instead of duplicating this literal n times."
+
+## [1.71.44] - 2021-10-20
+
+### Added
+
+- OData V2:
+  - Support for (Sub)Section properties: `visible`.
+  - Footer actions are now part of the schema. A node for header actions is visible even if there are no actions yet.
+  - ALP: Schema now comprises of entity properties for config `createWithParameterDialog`->`fields`
+  - OP: Added support for multiple flex changes in Form and Header Actions
+
+### Changed
+
+### Removed
+
+- OData V2:
+  - OVP: Removed `tab` property from `Stack` and `Link List` cards as view switch control is not supported
+
+### Fixed
+
+- OData V2:
+  - Add `visible` property to DataField types
+  - Replace alias of namespace definitions of header actions even for references that are not related to OData vocabularies.
+  - annotationPath definitions of header and footer actions.
+
+### Quality
+
+- Settings for sonarlint have been added.
+
+## [1.71.43] - 2021-10-06
+
+### Added
+
+- Annotation path `com.sap.vocabularies.UI.v1.HeaderInfo` added to ObjectPageHeader schema.
+- `i18nClassification` for `title`, `description` properties for `App.json` schema in V2.
+- OData V2:
+  - OVP: Added support for property `annotationPath` in Linklist card settings.
+  - OVP: property `requireAppAuthorization` is now supported for all card types.
+
+### Changed
+
+- README was 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}}".
+
+### Quality
+
+- Fix of vulnerabilities by upgrade of npm modules.
+- Fix of bugs and code smells reported by SonarQube.
+
+## [1.71.42] - 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 app specific 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".
+
+### Fixed
+
+- OData V2: 
+    - Invalid flexChanges are now ignored during sync, hence configs and pages files are created.
+
+### Quality
+
+- Bugs and code smells removed that had been detected by SonarQube.
+
+## [1.71.41] - 2021-09-08
+
+### Added
+
+- OData V2:
+  - OVP: Added support for property `dataPointAnnotationPath` in ListCard settings
+
 ## [1.71.40] - 2021-08-25
 
 ### Added
@@ -32,19 +114,13 @@ 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
 
 - Object Page schema generation crash when 'Facets' entry is not defined for 'CollectionFacet'
 - Page schema generation - `annotationPath` was missing for `table/toolbar`
 
-### Quality
-
 ## [1.71.39] - 2021-08-12
 
 ### Added
@@ -70,10 +146,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.
@@ -91,12 +163,6 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 - 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.

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.