@sap/ux-specification 1.84.45 → 1.84.46

package/CHANGELOG.md

@@ -8,6 +8,46 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 *Official support of OData V4*
 
+## [1.84.46] - 2022-08-24
+
+### Added
+
+- OData V2:
+  - LR:
+
+### Changed
+
+- The specification module is now build with esbuild instead of webpack.
+The new build generates all type information into a types folder, which makes it easier to consume (but the consumption must be adapted). Examples:
+
+````
+import { PageType } from '@sap/ux-specification/dist/src/specification/common/'; 
+==>  import { PageType } from '@sap/ux-specification/types';
+
+import type { TableCustomColumns, TableCustomColumn } from '@sap/ux-specification/dist/src/v2';
+==> import type { TableCustomColumns, TableCustomColumn } from '@sap/ux-specification/types/v2';
+
+import { SectionPosition as SectionPositionV4 } from '@sap/ux-specification/dist/src/v4';
+==> import { SectionPosition as SectionPositionV4 } from '@sap/ux-specification/types/v4';
+````
+
+- OData V4:
+  - LR: Mark view properties `key`, `index` as hidden in schema
+
+### Removed
+
+### Deprecated
+
+### Fixed
+
+- OData V2:
+  - OP: Fixed incorrect generation of flexChanges in case of Form, Form Fields and Form Fields referenced from a navigation entity
+
+- OData V4:
+  - In some cases sections defined with PresentationVariants did not appear on the object page
+  - The resolution of alias definitions using the @SAP__ prefix was not correct, leading also to gaps in the elements that were considered
+  - LR: Schema now considers default visualation `UI.LineItem` if not defined in `SelectionPresentationVariant`
+
 ## [1.84.45] - 2022-08-11
 
 ### Added
@@ -18,13 +58,17 @@ This project adheres to [Semantic Versioning](http://semver.org/) and the change
 
 ### Changed
 
-- OData V4: Wit API version 4 of specification - introduced with the given version - the way how routes are represented in the app.json changes: before the pattern was
+- OData V4: With API version 4 of specification - introduced with the given version - the way how routes are represented in the app.json changes: before the pattern was
   `route: key`, now it follows the manifest syntax  
+
+  ```
   key: {
       route: route
   }
+  ```
+
   The switch to an object representation allows to also include other target information like "outbound".
-- OData V4: as long as no views are defined in manifest, the showCounts property is not part of the schema, except if it is already maintained. 
+- OData V4: as long as no views are defined in manifest, the showCounts property is not part of the schema, except if it is already maintained.
 - OData V2:
   - Mark custom column 'columnIndex' property as hidden