@openui5/ts-types 1.138.0 → 1.140.0

package/README.md

@@ -6,7 +6,7 @@ This npm package contains the types signatures (based on deprecated globals, see
 
 <b>NOTE:</b> "based on globals" means that it supports the usage of the global "sap" object and the huge tree below this global object containing all modules and controls. But this usage is <b>no longer recommended</b>. In traditional JavaScript, UI5 application code should use the asynchronous `sap.ui.define()`/`sap.ui.require()` calls instead and for TypeScript code we recommend using ES6 module syntax provided by the [@openui5/types](https://www.npmjs.com/package/@openui5/types) package. So better use that one instead of this package.
 
-The central entry point for all information about using UI5 with TypeScript (incl. sample apps and templates) is at https://sap.github.io/ui5-typescript.
+The central entry point for all information about using UI5 with TypeScript (incl. sample apps and templates) is at https://ui5.github.io/typescript.
 
 ## Status
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openui5/ts-types",
-  "version": "1.138.0",
+  "version": "1.140.0",
   "description": "OpenUI5 TypeScript Definitions",
   "homepage": "https://openui5.org",
   "author": "SAP SE (https://www.sap.com)",

package/types/sap.f.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.138.0
+// For Library Version: 1.140.0
 
 declare namespace sap {
   /**
@@ -3310,16 +3310,24 @@ declare namespace sap {
 
     namespace routing {
       /**
-       * The `sap.f.routing.Router` class is intended to be used with `{@link sap.f.FlexibleColumnLayout}` as
-       * a root control.
+       * The `sap.f.routing.Router` extends the capabilities of the standard `{@link sap.ui.core.routing.Router}`
+       * to support flexible and responsive layouts based on `{@link sap.f.FlexibleColumnLayout}` as the root
+       * control.
+       *
+       * This router enables advanced navigation scenarios tailored to flexible column layouts, such as changing
+       * both the layout type (e.g., OneColumn, TwoColumnsMidExpanded) and the currently displayed views within
+       * individual columns.
        *
-       * The difference to the `{@link sap.ui.core.routing.Router}` are the `level`, `transition`, and `transitionParameters`
-       * properties that you can specify in every Route or Target created by this router.
+       * Compared to `{@link sap.ui.core.routing.Router}`, it adds support for additional target properties:
        *
-       * The difference to the `{@link sap.m.routing.Router}` is the additional `layout` property that can be
-       * specified in every Route, in which case it is applied to the root control. Also, the `sap.f.routing.Router`
-       * supports navigations that involve both change of `{@link sap.f.LayoutType}` and change of the current
-       * page within a single column of the `sap.f.FlexibleColumnLayout`.
+       * 	 - `level`: Defines the hierarchical level of the target view for proper history and back navigation
+       *     handling
+       * 	 - `transition`: Specifies the type of transition animation between views (e.g., `slide`, `fade`)
+       * 	 - `transitionParameters`: Custom parameters for transitions
+       *
+       * Compared to `{@link sap.m.routing.Router}`, it further introduces a `layout` property on each route,
+       * allowing you to define the desired `{@link sap.f.LayoutType}` to be applied to the `FlexibleColumnLayout`
+       * root control during navigation.
        *
        * See `{@link sap.ui.core.routing.Router}` for the constructor arguments.
        *
@@ -9006,8 +9014,8 @@ declare namespace sap {
 
       /**
        * The `DynamicPageTitle` actions.
-       * **Note:** The `actions` aggregation accepts any UI5 control, but it`s recommended to use controls, suitable
-       * for {@link sap.m.Toolbar} and {@link sap.m.OverflowToolbar}.
+       * **Note:** The `actions` aggregation accepts any UI5 control. However, it is best to use buttons or controls
+       * that work well inside toolbars, such as those typically used with {@link sap.m.Toolbar} and {@link sap.m.OverflowToolbar}.
        *
        * **Note:** If the `snappedTitleOnMobile` aggregation is set, its content overrides this aggregation when
        * the control is viewed on a phone mobile device and the `DynamicPageHeader` is in its collapsed (snapped)
@@ -9858,6 +9866,18 @@ declare namespace sap {
         | sap.ui.base.ManagedObject.PropertyBindingInfo
         | `{${string}}`;
 
+      /**
+       * Defines the image to be displayed as graphical element within the `ProductSwitchItem`.
+       *
+       * **Note:** This property takes precedence over the `src` property.
+       *
+       * @since 1.140
+       */
+      imageSrc?:
+        | sap.ui.core.URI
+        | sap.ui.base.ManagedObject.PropertyBindingInfo
+        | `{${string}}`;
+
       /**
        * Determines the title of the `ProductSwitchItem`.
        */
@@ -13644,8 +13664,8 @@ declare namespace sap {
        * Gets content of aggregation {@link #getActions actions}.
        *
        * The `DynamicPageTitle` actions.
-       * **Note:** The `actions` aggregation accepts any UI5 control, but it`s recommended to use controls, suitable
-       * for {@link sap.m.Toolbar} and {@link sap.m.OverflowToolbar}.
+       * **Note:** The `actions` aggregation accepts any UI5 control. However, it is best to use buttons or controls
+       * that work well inside toolbars, such as those typically used with {@link sap.m.Toolbar} and {@link sap.m.OverflowToolbar}.
        *
        * **Note:** If the `snappedTitleOnMobile` aggregation is set, its content overrides this aggregation when
        * the control is viewed on a phone mobile device and the `DynamicPageHeader` is in its collapsed (snapped)
@@ -19680,6 +19700,18 @@ declare namespace sap {
        * @returns Metadata object describing this class
        */
       static getMetadata(): sap.ui.core.ElementMetadata;
+      /**
+       * Gets current value of property {@link #getImageSrc imageSrc}.
+       *
+       * Defines the image to be displayed as graphical element within the `ProductSwitchItem`.
+       *
+       * **Note:** This property takes precedence over the `src` property.
+       *
+       * @since 1.140
+       *
+       * @returns Value of property `imageSrc`
+       */
+      getImageSrc(): sap.ui.core.URI;
       /**
        * Gets current value of property {@link #getSrc src}.
        *
@@ -19732,6 +19764,25 @@ declare namespace sap {
        * @returns Value of property `title`
        */
       getTitle(): string;
+      /**
+       * Sets a new value for property {@link #getImageSrc imageSrc}.
+       *
+       * Defines the image to be displayed as graphical element within the `ProductSwitchItem`.
+       *
+       * **Note:** This property takes precedence over the `src` property.
+       *
+       * When called with a value of `null` or `undefined`, the default value of the property will be restored.
+       *
+       * @since 1.140
+       *
+       * @returns Reference to `this` in order to allow method chaining
+       */
+      setImageSrc(
+        /**
+         * New value for property `imageSrc`
+         */
+        sImageSrc?: sap.ui.core.URI
+      ): this;
       /**
        * Sets a new value for property {@link #getSrc src}.
        *