@sapui5/ts-types 1.152.0 → 1.153.0

package/types/sap.ui.core.d.ts

@@ -279,7 +279,7 @@ declare namespace sap {
     "sap/ui/thirdparty/qunit-2": undefined;
   }
 }
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare module "sap/base/assert" {
   /**
@@ -8581,6 +8581,12 @@ declare namespace sap {
                * @since 1.37.0
                */
               waitFor?: Promise<any> | Array<Promise<any>>;
+              /**
+               * a marker to indicate that the Component is a launcher, e.g. the fiori launchpad (experimental setting)
+               *
+               * @since 1.153.0
+               */
+              isLauncher?: boolean;
             };
             /**
              * Controls when and from where to load the manifest for the Component. When set to any truthy value, the
@@ -18829,6 +18835,151 @@ declare namespace sap {
                 ]
               | null;
           }
+
+          /**
+           * The format options type for date formats.
+           */
+          type DateFormatOptions =
+            sap.ui.core.format.DateFormat.IntervalFormatOptions & {
+              /**
+               * A date pattern in {@link https://unicode.org/reports/tr35/tr35-dates.html#table-date-field-symbol-table LDML format}.
+               * It is not verified whether the pattern represents only a date.
+               */
+              pattern?: string;
+              /**
+               * The locale-dependent formatting style for the date, used if no `pattern` is provided.
+               */
+              style?: "short" | "medium" | "long" | "full";
+            };
+
+          /**
+           * The base format options for date formats.
+           */
+          type FormatOptions = {
+            /**
+             * The calendar type used to format and parse the date. By default, this value is taken from the configuration
+             * (see {@link module:sap/base/i18n/Formatting.setCalendarType Formatting.setCalendarType}), or - if not
+             * set - calculated based on the current locale, see {@link module:sap/base/i18n/Formatting.getCalendarType Formatting.getCalendarType}.
+             */
+            calendarType?: import("sap/base/i18n/date/CalendarType").default;
+            /**
+             * Specifies the calendar week numbering. If specified, this overwrites `firstDayOfWeek` and `minimalDaysInFirstWeek`.
+             *
+             * @since 1.108.0
+             */
+            calendarWeekNumbering?: import("sap/base/i18n/date/CalendarWeekNumbering").default;
+            /**
+             * Specifies the first day of the week starting with `0` (which is Sunday). If not defined, the value is
+             * taken from the locale, see {@link sap.ui.core.LocaleData.getFirstDayOfWeek LocaleData.getFirstDayOfWeek}.
+             *
+             * @since 1.105.0
+             */
+            firstDayOfWeek?: int;
+            /**
+             * Contains pattern symbols (for example, "yMMMd" or "Hms") that are converted into the pattern in the used
+             * locale which matches the wanted symbols best. The symbols must be in canonical order: Era (G), Year (y/Y),
+             * Quarter (q/Q), Month (M/L), Week (w), Day-Of-Week (E/e/c), Day (d), Hour (h/H/k/K/j/J), Minute (m), Second
+             * (s), Timezone (z/Z/v/V/O/X/x) See {@link https://unicode.org/reports/tr35/tr35-dates.html#availableFormats_appendItems Unicode Locale Data Markup Language (LDML): Elements availableFormats, appendItems}.
+             *
+             * @since 1.34.0
+             */
+            format?: string;
+            /**
+             * Minimal days at the beginning of the year that define the first calendar week. If not defined, the value
+             * is taken from the locale, see {@link sap.ui.core.LocaleData.getMinimalDaysInFirstWeek LocaleData.getMinimalDaysInFirstWeek}.
+             *
+             * @since 1.105.0
+             */
+            minimalDaysInFirstWeek?: int;
+            /**
+             * If `true`, the date is formatted relatively to today's date if it is within the given `relativeRange`.
+             *  **Example:**
+             * 	 - Today is the **2026-01-05**
+             * 	 - `relative` is set to `true`
+             * 	 - `relativeRange` is set to `[-2, 2]`
+             * 	 - This means that only dates two days prior or after **2026-01-05** are formatted in the relative format
+             *
+             * 	 - For example, date **2026-01-07** would be formatted to `"in 2 days"` for the English locale
+             * 	 - Whereas, the **2026-01-08** would be formatted in the non-relative format as it is out of the `relativeRange`
+             */
+            relative?: boolean;
+            /**
+             * The date range in which the relative formatting is applied. It depends on the `relativeScale`. For example,
+             * `relativeScale="day"` and `relativeRange=[-2, 2]` means only dates that are 2 **days** before or 2 **days**
+             * after today's date are formatted relatively. If no range given, the range is determined depending on
+             * the `relativeScale`. This is the list of defaults depending on the `relativeScale`:
+             * 	 - `relativeScale="second"`, `relativeRange=[-60, 60]`
+             * 	 - `relativeScale="minute"`, `relativeRange=[-60, 60]`
+             * 	 - `relativeScale="hour"`, `relativeRange=[-24, 24]`
+             * 	 - `relativeScale="day"`, `relativeRange=[-6, 6]`
+             * 	 - `relativeScale="week"`, `relativeRange=[-4, 4]`
+             * 	 - `relativeScale="month"`, `relativeRange=[-12, 12]`
+             * 	 - `relativeScale="year"`, `relativeRange=[-10, 10]`  Otherwise, when `relativeScale` is set to
+             *     `auto`, all dates are formatted relatively.
+             */
+            relativeRange?: int[];
+            /**
+             * If `auto` is set, a new relative time format is switched on for all Date/Time instances. The relative
+             * scale is chosen depending on the difference between the given date and now.
+             */
+            relativeScale?:
+              | "auto"
+              | "year"
+              | "month"
+              | "week"
+              | "day"
+              | "hour"
+              | "minute"
+              | "second";
+            /**
+             * The style of the relative format.
+             *
+             * @since 1.34.4
+             */
+            relativeStyle?: "narrow" | "short" | "wide";
+            /**
+             * If `true`, parsing validates that the value is a valid date. For example, the parsing of an overflowing
+             * value like **2026-01-32** returns `null` instead of **2026-02-01**.
+             */
+            strictParsing?: boolean;
+            /**
+             * If `true`, the date is formatted and parsed as UTC instead of the local timezone.
+             */
+            UTC?: boolean;
+          };
+
+          /**
+           * Extends the format options for a single date, time, or date and time to include interval-related settings.
+           */
+          type IntervalFormatOptions =
+            sap.ui.core.format.DateFormat.FormatOptions & {
+              /**
+               * If `true`, the {@link sap.ui.core.format.DateFormat#format format} method expects an array with two dates
+               * as the first argument and formats them as an interval. For example, the interval "Jan 10, 2008 - Jan
+               * 12, 2008" is formatted as "Jan 10-12, 2008" if the `format` option is set to `"yMMMd"`. If no `format`
+               * is set, the two dates are formatted separately and concatenated with a locale-dependent pattern.
+               *
+               * @since 1.48.0
+               */
+              interval?: boolean;
+              /**
+               * A delimiter for intervals. A specific interval format is created with a given delimiter.
+               *  **Example:** If `oFormatOptions.intervalDelimiter` is set to "...", the formatted result would be "Jan
+               * 10, 2008...Feb 12, 2008". **Note:** If this format option is set, the locale-specific interval notation
+               * is overridden. For example, "Jan 10 – Feb 12, 2008" becomes "Jan 10, 2008...Feb 12, 2008".
+               *
+               * @since 1.113.0
+               */
+              intervalDelimiter?: string;
+              /**
+               * Only relevant if `interval` is set to `true`. This allows you to pass an array with only one date object
+               * to the {@link sap.ui.core.format.DateFormat#format format} method, which is then formatted as a single
+               * value. For example, the value `[UI5Date.getInstance("2026-01-20")]` is formatted to `"Jan 20, 2026"`
+               * in the English locale. If the `pattern` format option is set to an interval pattern, the formatted result
+               * displays the value as an interval, but the dates of this interval are the same.
+               */
+              singleIntervalValue?: boolean;
+            };
         }
 
         namespace NumberFormat {
@@ -18899,7 +19050,7 @@ declare namespace sap {
               currencyCode?: boolean;
               /**
                * Can be set either to 'standard' (the default value) or to 'accounting' for an accounting-specific currency
-               * display
+               * display.
                */
               currencyContext?:
                 | "standard"
@@ -18960,18 +19111,17 @@ declare namespace sap {
                */
               preserveDecimals?: boolean;
               /**
-               * Defines whether the currency code/symbol is shown in the formatted string, e.g. true: "1.00 EUR", false:
-               * "1.00" for locale "en" If both `showMeasure` and `showNumber` are false, an empty string is returned
+               * Defines whether the currency code/symbol is shown in the formatted string, for example, `1 EUR` for locale
+               * `"en"`. `NumberFormat.getCurrencyInstance({showMeasure: true}).format(1, "EUR"); // "1.00 EUR"` `NumberFormat.getCurrencyInstance({showMeasure:
+               * false}).format(1, "EUR"); // "1.00"` If both `showMeasure` and `showNumber` are false, an empty string
+               * is returned.
                */
               showMeasure?: boolean;
               /**
-               * Defines whether the number is shown as part of the result string, e.g. 1 EUR for locale "en"
-               * ```javascript
-               * `NumberFormat.getCurrencyInstance({showNumber: true}).format(1, "EUR"); // "1.00 EUR"````
-               *
-               * ```javascript
-               * `NumberFormat.getCurrencyInstance({showNumber: false}).format(1, "EUR"); // "EUR"````
-               *  If both `showMeasure` and `showNumber` are false, an empty string is returned
+               * Defines whether the number is shown as part of the result string, for example, `1 EUR` for locale `"en"`.
+               * `NumberFormat.getCurrencyInstance({showNumber: true}).format(1, "EUR"); // "1.00 EUR"` `NumberFormat.getCurrencyInstance({showNumber:
+               * false}).format(1, "EUR"); // "EUR"` If both `showMeasure` and `showNumber` are false, an empty string
+               * is returned.
                */
               showNumber?: boolean;
               /**
@@ -19201,6 +19351,7 @@ declare namespace sap {
               /**
                * Defines a set of custom units, for example:
                * ```javascript
+               *
                * {"electric-inductance": {
                *      "displayName": "henry",
                *      "unitPattern-count-one": "{0} H",
@@ -19209,7 +19360,8 @@ declare namespace sap {
                *      "decimals": 2,
                *      "precision": 4
                *   }
-               * }```
+               * }
+               * ```
                */
               customUnits?: Record<string, object>;
               /**
@@ -19257,29 +19409,17 @@ declare namespace sap {
                */
               preserveDecimals?: boolean;
               /**
-               * Defines whether the unit of measure is shown in the formatted string, for example 1 day for locale "en"
-               *
-               * ```javascript
-               * NumberFormat.getUnitInstance({showMeasure: true})
-               *     .format(1, "duration-day"); // "1 day"```
-               *
-               * ```javascript
-               * NumberFormat.getUnitInstance({showMeasure: false})
-               *     .format(1, "duration-day"); // "1"```
-               *  If both `showMeasure` and `showNumber` are set to false, an empty string is returned.
+               * Defines whether the unit of measure is shown in the formatted string, for example, `1 day` for locale
+               * `"en"`. `NumberFormat.getUnitInstance({showMeasure: true}).format(1, "duration-day"); // "1 day"` `NumberFormat.getUnitInstance({showMeasure:
+               * false}).format(1, "duration-day"); // "1"` If both `showMeasure` and `showNumber` are set to false, an
+               * empty string is returned.
                */
               showMeasure?: boolean;
               /**
-               * Defines whether the number is shown as part of the formatted string, for example 1 day for locale "en"
-               *
-               * ```javascript
-               * NumberFormat.getUnitInstance({showNumber: true})
-               *     .format(1, "duration-day"); // "1 day"```
-               *
-               * ```javascript
-               * NumberFormat.getUnitInstance({showNumber: false})
-               *     .format(1, "duration-day"); // "day"```
-               *  If both `showMeasure` and `showNumber` are false, an empty string is returned
+               * Defines whether the number is shown as part of the formatted string, for example, `1 day` for locale
+               * `"en"`. `NumberFormat.getUnitInstance({showNumber: true}).format(1, "duration-day"); // "1 day"` `NumberFormat.getUnitInstance({showNumber:
+               * false}).format(1, "duration-day"); // "day"` If both `showMeasure` and `showNumber` are false, an empty
+               * string is returned.
                */
               showNumber?: boolean;
               /**
@@ -19322,92 +19462,7 @@ declare namespace sap {
             /**
              * Object which defines the format options
              */
-            oFormatOptions?: {
-              /**
-               * since 1.108.0 specifies the calendar week numbering. If specified, this overwrites `oFormatOptions.firstDayOfWeek`
-               * and `oFormatOptions.minimalDaysInFirstWeek`.
-               */
-              calendarWeekNumbering?: import("sap/base/i18n/date/CalendarWeekNumbering").default;
-              /**
-               * since 1.105.0 specifies the first day of the week starting with `0` (which is Sunday); if not defined,
-               * the value taken from the locale is used
-               */
-              firstDayOfWeek?: int;
-              /**
-               * since 1.105.0 minimal days at the beginning of the year which define the first calendar week; if not
-               * defined, the value taken from the locale is used
-               */
-              minimalDaysInFirstWeek?: int;
-              /**
-               * since 1.34.0 contains pattern symbols (e.g. "yMMMd" or "Hms") which will be converted into the pattern
-               * in the used locale, which matches the wanted symbols best. The symbols must be in canonical order, that
-               * is: Era (G), Year (y/Y), Quarter (q/Q), Month (M/L), Week (w), Day-Of-Week (E/e/c), Day (d), Hour (h/H/k/K/j/J),
-               * Minute (m), Second (s), Timezone (z/Z/v/V/O/X/x) See {@link https://unicode.org/reports/tr35/tr35-dates.html#availableFormats_appendItems Unicode Locale Data Markup Language (LDML): Elements availableFormats, appendItems}.
-               */
-              format?: string;
-              /**
-               * a data pattern in LDML format. It is not verified whether the pattern represents only a date.
-               */
-              pattern?: string;
-              /**
-               * can be either 'short, 'medium', 'long' or 'full'. If no pattern is given, a locale dependent default
-               * date pattern of that style is used from the LocaleData class.
-               */
-              style?: string;
-              /**
-               * if true, by parsing it is checked if the value is a valid date
-               */
-              strictParsing?: boolean;
-              /**
-               * if true, the date is formatted relatively to todays date if it is within the given day range, e.g. "today",
-               * "1 day ago", "in 5 days"
-               */
-              relative?: boolean;
-              /**
-               * the day range used for relative formatting. If `oFormatOptions.relativeScale` is set to default value
-               * 'day', the relativeRange is by default [-6, 6], which means only the last 6 days, today and the next
-               * 6 days are formatted relatively. Otherwise when `oFormatOptions.relativeScale` is set to 'auto', all
-               * dates are formatted relatively.
-               */
-              relativeRange?: int[];
-              /**
-               * if 'auto' is set, new relative time format is switched on for all Date/Time Instances. The relative scale
-               * is chosen depending on the difference between the given date and now.
-               */
-              relativeScale?: string;
-              /**
-               * since 1.32.10, 1.34.4 the style of the relative format. The valid values are "wide", "short", "narrow"
-               */
-              relativeStyle?: string;
-              /**
-               * since 1.48.0 if true, the {@link sap.ui.core.format.DateFormat#format format} method expects an array
-               * with two dates as the first argument and formats them as interval. Further interval "Jan 10, 2008 - Jan
-               * 12, 2008" will be formatted as "Jan 10-12, 2008" if the 'format' option is set with necessary symbols.
-               * Otherwise the two given dates are formatted separately and concatenated with local dependent pattern.
-               */
-              interval?: boolean;
-              /**
-               * Since 1.113.0, a delimiter for intervals. With a given interval delimiter a specific interval format
-               * is created. **Example:** If `oFormatOptions.intervalDelimiter` is set to "...", an interval would be
-               * given as "Jan 10, 2008...Feb 12, 2008". **Note:** If this format option is set, the locale-specific interval
-               * notation is overruled, for example "Jan 10 – Feb 12, 2008" becomes "Jan 10, 2008...Feb 12, 2008".
-               */
-              intervalDelimiter?: string;
-              /**
-               * Only relevant if oFormatOptions.interval is set to 'true'. This allows to pass an array with only one
-               * date object to the {@link sap.ui.core.format.DateFormat#format format} method.
-               */
-              singleIntervalValue?: boolean;
-              /**
-               * if true, the date is formatted and parsed as UTC instead of the local timezone
-               */
-              UTC?: boolean;
-              /**
-               * The calender type which is used to format and parse the date. This value is by default either set in
-               * configuration or calculated based on current locale.
-               */
-              calendarType?: import("sap/base/i18n/date/CalendarType").default;
-            },
+            oFormatOptions?: sap.ui.core.format.DateFormat.DateFormatOptions,
             /**
              * Locale to ask for locale specific texts/settings
              */
@@ -56870,9 +56925,9 @@ declare namespace sap {
              */
             constructor(
               /**
-               * Format options as defined in {@link sap.ui.core.format.DateFormat.getDateInstance}
+               * The format options
                */
-              oFormatOptions?: object,
+              oFormatOptions?: sap.ui.core.format.DateFormat.DateFormatOptions,
               /**
                * constraints; {@link #validateValue validateValue} throws an error if any constraint is violated
                */
@@ -75775,20 +75830,9 @@ declare namespace sap {
            */
           constructor(
             /**
-             * Formatting options. For a list of all available options, see {@link sap.ui.core.format.DateFormat.getDateInstance DateFormat}.
+             * The format options
              */
-            oFormatOptions?: {
-              /**
-               * Additional set of options used to create a second `DateFormat` object for conversions between string
-               * values in the data source (e.g. model) and `Date`. This second format object is used to convert from
-               * a model `string` to `Date` before converting the `Date` to `string` with the primary format object. Vice
-               * versa, this 'source' format is also used to format an already parsed external value (e.g. user input)
-               * into the string format that is expected by the data source. For a list of all available options, see
-               * {@link sap.ui.core.format.DateFormat.getDateInstance DateFormat}. In case an empty object is given, the
-               * default is the ISO date notation (yyyy-MM-dd).
-               */
-              source?: object;
-            },
+            oFormatOptions?: sap.ui.model.type.DateTypeFormatOptions,
             /**
              * Value constraints
              */
@@ -76885,6 +76929,24 @@ declare namespace sap {
             trailingCurrencyCode?: boolean;
           };
 
+        /**
+         * The format options for the `sap.ui.model.type.Date`.
+         */
+        type DateTypeFormatOptions =
+          sap.ui.core.format.DateFormat.DateFormatOptions & {
+            /**
+             * Additional set of format options for a second `DateFormat` object. This object handles conversions between
+             * string values in the data source (for example, model) and `Date` objects. These source options are used
+             * for two-way data binding:
+             * 	 - **Model to View:** Converts a string from the model to a `Date` object. Afterwards the main format
+             *     options are used to convert that `Date` object to a string for display.
+             * 	 - **View to Model:** Converts a parsed external value, for example, user input, into the string format
+             *     that the data source requires.  If an empty object is provided, the default format is the ISO date
+             *     notation (yyyy-MM-dd).
+             */
+            source?: sap.ui.core.format.DateFormat.DateFormatOptions;
+          };
+
         /**
          * The format options of the {@link sap.ui.model.type.Float} type.
          */
@@ -88880,6 +88942,12 @@ declare namespace sap {
 
     "sap/ui/core/Placeholder": undefined;
 
+    "sap/ui/core/popover/PopoverFlipMode": undefined;
+
+    "sap/ui/core/popover/PopoverPhysicalSide": undefined;
+
+    "sap/ui/core/popover/Positioning": undefined;
+
     "sap/ui/core/Popup": undefined;
 
     "sap/ui/core/postmessage/Bus": undefined;

package/types/sap.ui.dt.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {
   interface IUI5DefineDependencyNames {

package/types/sap.ui.export.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {
   namespace ui {
@@ -692,6 +692,7 @@ declare namespace sap {
          *         title: 'Some random title',
          *         modifiedBy: 'John Doe',
          *         metaSheetName: 'Custom metadata',
+         *         rtl: true,
          *         metainfo: [
          *           {
          *             name: 'Grouped Properties',
@@ -1070,7 +1071,9 @@ declare namespace sap {
          */
         label?: string;
         /**
-         * Field name or array of field names in the data source feed.
+         * Field name or array of field names in the data source feed. A field that references a to-many navigation
+         * property (a 1:N association) is exported as multiple values within a single cell. The values are joined
+         * by the `separator` and, if a `template` is provided, formatted per value. Since 1.152.
          */
         property?: string | string[];
         /**
@@ -1164,6 +1167,10 @@ declare namespace sap {
          * a translated read-only suffix so the lock state is visible and announced by screen readers. Since: 1.152.
          */
         readOnly?: boolean;
+        /**
+         * Separator that joins the values of a multi value column. Since 1.152.
+         */
+        separator?: string;
       };
 
       type SpreadsheetSettings = {
@@ -1203,6 +1210,11 @@ declare namespace sap {
              * The label of the metadata sheet. The sheet will not be shown unless metadata entries are provided
              */
             metaSheetName?: string;
+            /**
+             * Whether the exported datasheet uses a right-to-left layout. Defaults to the current UI5 RTL configuration.
+             * @since 1.153
+             */
+            rtl?: boolean;
             /**
              * Metadata groups with key/value pairs.
              */

package/types/sap.ui.fl.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {
   namespace ui {

package/types/sap.ui.generic.app.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {
   namespace ui {

package/types/sap.ui.generic.template.d.ts

@@ -1,3 +1,3 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {}

package/types/sap.ui.geomap.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare module "sap/ui/geomap/gen/sap_webcomponents/geomap/dist/SapGeomap" {
   /**

package/types/sap.ui.integration.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {
   namespace ui {

package/types/sap.ui.joule.frontend.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {
   namespace ui {

package/types/sap.ui.layout.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.152.0
+// For Library Version: 1.153.0
 
 declare namespace sap {
   namespace ui {