@sapui5/ts-types 1.151.1 → 1.153.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (68) hide show
  1. package/package.json +1 -1
  2. package/types/index.d.ts +4 -4
  3. package/types/sap.apf.d.ts +1 -1
  4. package/types/sap.ca.ui.d.ts +1 -1
  5. package/types/sap.chart.d.ts +1 -1
  6. package/types/sap.collaboration.d.ts +1 -1
  7. package/types/sap.esh.search.ui.d.ts +18 -1
  8. package/types/sap.f.d.ts +1189 -292
  9. package/types/sap.fe.ariba.d.ts +1 -1
  10. package/types/sap.fe.base.d.ts +1 -1
  11. package/types/sap.fe.controls.d.ts +1 -1
  12. package/types/sap.fe.core.d.ts +104 -9
  13. package/types/sap.fe.ina.d.ts +1 -1
  14. package/types/sap.fe.macros.d.ts +238 -52
  15. package/types/sap.fe.navigation.d.ts +1 -1
  16. package/types/sap.fe.placeholder.d.ts +1 -1
  17. package/types/sap.fe.plugins.managecache.d.ts +1 -1
  18. package/types/sap.fe.templates.d.ts +12 -2
  19. package/types/sap.fe.test.d.ts +15 -1
  20. package/types/sap.fe.tools.d.ts +1 -1
  21. package/types/sap.feedback.ui.d.ts +1 -1
  22. package/types/sap.gantt.d.ts +303 -24
  23. package/types/sap.insights.d.ts +1 -1
  24. package/types/{mobile-1.151.0-d.ts → sap.m.d.ts} +368 -32
  25. package/types/sap.makit.d.ts +1 -1
  26. package/types/sap.me.d.ts +1 -1
  27. package/types/sap.ndc.d.ts +1 -1
  28. package/types/sap.ovp.d.ts +1 -1
  29. package/types/sap.rules.ui.d.ts +1 -1
  30. package/types/sap.sac.df.d.ts +1 -1
  31. package/types/sap.suite.ui.commons.d.ts +926 -14
  32. package/types/sap.suite.ui.generic.template.d.ts +31 -1
  33. package/types/sap.suite.ui.microchart.d.ts +1 -1
  34. package/types/sap.tnt.d.ts +1 -1
  35. package/types/sap.ui.codeeditor.d.ts +1 -1
  36. package/types/sap.ui.commons.d.ts +1 -1
  37. package/types/sap.ui.comp.d.ts +4 -2
  38. package/types/{core-1.151.0-d.ts → sap.ui.core.d.ts} +375 -144
  39. package/types/{dt-1.151.0-d.ts → sap.ui.dt.d.ts} +1 -1
  40. package/types/sap.ui.export.d.ts +20 -2
  41. package/types/sap.ui.fl.d.ts +1 -1
  42. package/types/sap.ui.generic.app.d.ts +1 -1
  43. package/types/sap.ui.generic.template.d.ts +1 -1
  44. package/types/sap.ui.geomap.d.ts +1 -1
  45. package/types/sap.ui.integration.d.ts +101 -325
  46. package/types/sap.ui.joule.frontend.d.ts +1 -1
  47. package/types/sap.ui.layout.d.ts +1 -1
  48. package/types/{mdc-1.151.0-d.ts → sap.ui.mdc.d.ts} +6646 -5514
  49. package/types/sap.ui.richtexteditor.d.ts +1 -1
  50. package/types/sap.ui.rta.d.ts +10 -2
  51. package/types/sap.ui.suite.d.ts +1 -1
  52. package/types/sap.ui.support.d.ts +1 -1
  53. package/types/sap.ui.table.d.ts +63 -1
  54. package/types/sap.ui.testrecorder.d.ts +1 -1
  55. package/types/sap.ui.unified.d.ts +60 -1
  56. package/types/sap.ui.ux3.d.ts +1 -1
  57. package/types/sap.ui.vbm.d.ts +1 -1
  58. package/types/sap.ui.vk.d.ts +1 -1
  59. package/types/sap.ui.vtm.d.ts +1 -1
  60. package/types/sap.uiext.inbox.d.ts +1 -1
  61. package/types/sap.ushell.d.ts +183 -56
  62. package/types/sap.ushell_abap.d.ts +1 -1
  63. package/types/sap.uxap.d.ts +1 -1
  64. package/types/sap.viz.d.ts +1 -1
  65. package/types/sap.webanalytics.core.d.ts +1 -1
  66. package/types/sap.zen.commons.d.ts +1 -1
  67. package/types/sap.zen.crosstab.d.ts +1 -1
  68. package/types/sap.zen.dsh.d.ts +1 -1
@@ -279,7 +279,7 @@ declare namespace sap {
279
279
  "sap/ui/thirdparty/qunit-2": undefined;
280
280
  }
281
281
  }
282
- // For Library Version: 1.151.0
282
+ // For Library Version: 1.153.0
283
283
 
284
284
  declare module "sap/base/assert" {
285
285
  /**
@@ -8581,6 +8581,12 @@ declare namespace sap {
8581
8581
  * @since 1.37.0
8582
8582
  */
8583
8583
  waitFor?: Promise<any> | Array<Promise<any>>;
8584
+ /**
8585
+ * a marker to indicate that the Component is a launcher, e.g. the fiori launchpad (experimental setting)
8586
+ *
8587
+ * @since 1.153.0
8588
+ */
8589
+ isLauncher?: boolean;
8584
8590
  };
8585
8591
  /**
8586
8592
  * 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 {
18829
18835
  ]
18830
18836
  | null;
18831
18837
  }
18838
+
18839
+ /**
18840
+ * The format options type for date formats.
18841
+ */
18842
+ type DateFormatOptions =
18843
+ sap.ui.core.format.DateFormat.IntervalFormatOptions & {
18844
+ /**
18845
+ * A date pattern in {@link https://unicode.org/reports/tr35/tr35-dates.html#table-date-field-symbol-table LDML format}.
18846
+ * It is not verified whether the pattern represents only a date.
18847
+ */
18848
+ pattern?: string;
18849
+ /**
18850
+ * The locale-dependent formatting style for the date, used if no `pattern` is provided.
18851
+ */
18852
+ style?: "short" | "medium" | "long" | "full";
18853
+ };
18854
+
18855
+ /**
18856
+ * The base format options for date formats.
18857
+ */
18858
+ type FormatOptions = {
18859
+ /**
18860
+ * The calendar type used to format and parse the date. By default, this value is taken from the configuration
18861
+ * (see {@link module:sap/base/i18n/Formatting.setCalendarType Formatting.setCalendarType}), or - if not
18862
+ * set - calculated based on the current locale, see {@link module:sap/base/i18n/Formatting.getCalendarType Formatting.getCalendarType}.
18863
+ */
18864
+ calendarType?: import("sap/base/i18n/date/CalendarType").default;
18865
+ /**
18866
+ * Specifies the calendar week numbering. If specified, this overwrites `firstDayOfWeek` and `minimalDaysInFirstWeek`.
18867
+ *
18868
+ * @since 1.108.0
18869
+ */
18870
+ calendarWeekNumbering?: import("sap/base/i18n/date/CalendarWeekNumbering").default;
18871
+ /**
18872
+ * Specifies the first day of the week starting with `0` (which is Sunday). If not defined, the value is
18873
+ * taken from the locale, see {@link sap.ui.core.LocaleData.getFirstDayOfWeek LocaleData.getFirstDayOfWeek}.
18874
+ *
18875
+ * @since 1.105.0
18876
+ */
18877
+ firstDayOfWeek?: int;
18878
+ /**
18879
+ * Contains pattern symbols (for example, "yMMMd" or "Hms") that are converted into the pattern in the used
18880
+ * locale which matches the wanted symbols best. The symbols must be in canonical order: Era (G), Year (y/Y),
18881
+ * 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
18882
+ * (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}.
18883
+ *
18884
+ * @since 1.34.0
18885
+ */
18886
+ format?: string;
18887
+ /**
18888
+ * Minimal days at the beginning of the year that define the first calendar week. If not defined, the value
18889
+ * is taken from the locale, see {@link sap.ui.core.LocaleData.getMinimalDaysInFirstWeek LocaleData.getMinimalDaysInFirstWeek}.
18890
+ *
18891
+ * @since 1.105.0
18892
+ */
18893
+ minimalDaysInFirstWeek?: int;
18894
+ /**
18895
+ * If `true`, the date is formatted relatively to today's date if it is within the given `relativeRange`.
18896
+ * **Example:**
18897
+ * - Today is the **2026-01-05**
18898
+ * - `relative` is set to `true`
18899
+ * - `relativeRange` is set to `[-2, 2]`
18900
+ * - This means that only dates two days prior or after **2026-01-05** are formatted in the relative format
18901
+ *
18902
+ * - For example, date **2026-01-07** would be formatted to `"in 2 days"` for the English locale
18903
+ * - Whereas, the **2026-01-08** would be formatted in the non-relative format as it is out of the `relativeRange`
18904
+ */
18905
+ relative?: boolean;
18906
+ /**
18907
+ * The date range in which the relative formatting is applied. It depends on the `relativeScale`. For example,
18908
+ * `relativeScale="day"` and `relativeRange=[-2, 2]` means only dates that are 2 **days** before or 2 **days**
18909
+ * after today's date are formatted relatively. If no range given, the range is determined depending on
18910
+ * the `relativeScale`. This is the list of defaults depending on the `relativeScale`:
18911
+ * - `relativeScale="second"`, `relativeRange=[-60, 60]`
18912
+ * - `relativeScale="minute"`, `relativeRange=[-60, 60]`
18913
+ * - `relativeScale="hour"`, `relativeRange=[-24, 24]`
18914
+ * - `relativeScale="day"`, `relativeRange=[-6, 6]`
18915
+ * - `relativeScale="week"`, `relativeRange=[-4, 4]`
18916
+ * - `relativeScale="month"`, `relativeRange=[-12, 12]`
18917
+ * - `relativeScale="year"`, `relativeRange=[-10, 10]` Otherwise, when `relativeScale` is set to
18918
+ * `auto`, all dates are formatted relatively.
18919
+ */
18920
+ relativeRange?: int[];
18921
+ /**
18922
+ * If `auto` is set, a new relative time format is switched on for all Date/Time instances. The relative
18923
+ * scale is chosen depending on the difference between the given date and now.
18924
+ */
18925
+ relativeScale?:
18926
+ | "auto"
18927
+ | "year"
18928
+ | "month"
18929
+ | "week"
18930
+ | "day"
18931
+ | "hour"
18932
+ | "minute"
18933
+ | "second";
18934
+ /**
18935
+ * The style of the relative format.
18936
+ *
18937
+ * @since 1.34.4
18938
+ */
18939
+ relativeStyle?: "narrow" | "short" | "wide";
18940
+ /**
18941
+ * If `true`, parsing validates that the value is a valid date. For example, the parsing of an overflowing
18942
+ * value like **2026-01-32** returns `null` instead of **2026-02-01**.
18943
+ */
18944
+ strictParsing?: boolean;
18945
+ /**
18946
+ * If `true`, the date is formatted and parsed as UTC instead of the local timezone.
18947
+ */
18948
+ UTC?: boolean;
18949
+ };
18950
+
18951
+ /**
18952
+ * Extends the format options for a single date, time, or date and time to include interval-related settings.
18953
+ */
18954
+ type IntervalFormatOptions =
18955
+ sap.ui.core.format.DateFormat.FormatOptions & {
18956
+ /**
18957
+ * If `true`, the {@link sap.ui.core.format.DateFormat#format format} method expects an array with two dates
18958
+ * as the first argument and formats them as an interval. For example, the interval "Jan 10, 2008 - Jan
18959
+ * 12, 2008" is formatted as "Jan 10-12, 2008" if the `format` option is set to `"yMMMd"`. If no `format`
18960
+ * is set, the two dates are formatted separately and concatenated with a locale-dependent pattern.
18961
+ *
18962
+ * @since 1.48.0
18963
+ */
18964
+ interval?: boolean;
18965
+ /**
18966
+ * A delimiter for intervals. A specific interval format is created with a given delimiter.
18967
+ * **Example:** If `oFormatOptions.intervalDelimiter` is set to "...", the formatted result would be "Jan
18968
+ * 10, 2008...Feb 12, 2008". **Note:** If this format option is set, the locale-specific interval notation
18969
+ * is overridden. For example, "Jan 10 – Feb 12, 2008" becomes "Jan 10, 2008...Feb 12, 2008".
18970
+ *
18971
+ * @since 1.113.0
18972
+ */
18973
+ intervalDelimiter?: string;
18974
+ /**
18975
+ * Only relevant if `interval` is set to `true`. This allows you to pass an array with only one date object
18976
+ * to the {@link sap.ui.core.format.DateFormat#format format} method, which is then formatted as a single
18977
+ * value. For example, the value `[UI5Date.getInstance("2026-01-20")]` is formatted to `"Jan 20, 2026"`
18978
+ * in the English locale. If the `pattern` format option is set to an interval pattern, the formatted result
18979
+ * displays the value as an interval, but the dates of this interval are the same.
18980
+ */
18981
+ singleIntervalValue?: boolean;
18982
+ };
18832
18983
  }
18833
18984
 
18834
18985
  namespace NumberFormat {
@@ -18899,7 +19050,7 @@ declare namespace sap {
18899
19050
  currencyCode?: boolean;
18900
19051
  /**
18901
19052
  * Can be set either to 'standard' (the default value) or to 'accounting' for an accounting-specific currency
18902
- * display
19053
+ * display.
18903
19054
  */
18904
19055
  currencyContext?:
18905
19056
  | "standard"
@@ -18960,18 +19111,17 @@ declare namespace sap {
18960
19111
  */
18961
19112
  preserveDecimals?: boolean;
18962
19113
  /**
18963
- * Defines whether the currency code/symbol is shown in the formatted string, e.g. true: "1.00 EUR", false:
18964
- * "1.00" for locale "en" If both `showMeasure` and `showNumber` are false, an empty string is returned
19114
+ * Defines whether the currency code/symbol is shown in the formatted string, for example, `1 EUR` for locale
19115
+ * `"en"`. `NumberFormat.getCurrencyInstance({showMeasure: true}).format(1, "EUR"); // "1.00 EUR"` `NumberFormat.getCurrencyInstance({showMeasure:
19116
+ * false}).format(1, "EUR"); // "1.00"` If both `showMeasure` and `showNumber` are false, an empty string
19117
+ * is returned.
18965
19118
  */
18966
19119
  showMeasure?: boolean;
18967
19120
  /**
18968
- * Defines whether the number is shown as part of the result string, e.g. 1 EUR for locale "en"
18969
- * ```javascript
18970
- * `NumberFormat.getCurrencyInstance({showNumber: true}).format(1, "EUR"); // "1.00 EUR"````
18971
- *
18972
- * ```javascript
18973
- * `NumberFormat.getCurrencyInstance({showNumber: false}).format(1, "EUR"); // "EUR"````
18974
- * If both `showMeasure` and `showNumber` are false, an empty string is returned
19121
+ * Defines whether the number is shown as part of the result string, for example, `1 EUR` for locale `"en"`.
19122
+ * `NumberFormat.getCurrencyInstance({showNumber: true}).format(1, "EUR"); // "1.00 EUR"` `NumberFormat.getCurrencyInstance({showNumber:
19123
+ * false}).format(1, "EUR"); // "EUR"` If both `showMeasure` and `showNumber` are false, an empty string
19124
+ * is returned.
18975
19125
  */
18976
19126
  showNumber?: boolean;
18977
19127
  /**
@@ -19201,6 +19351,7 @@ declare namespace sap {
19201
19351
  /**
19202
19352
  * Defines a set of custom units, for example:
19203
19353
  * ```javascript
19354
+ *
19204
19355
  * {"electric-inductance": {
19205
19356
  * "displayName": "henry",
19206
19357
  * "unitPattern-count-one": "{0} H",
@@ -19209,7 +19360,8 @@ declare namespace sap {
19209
19360
  * "decimals": 2,
19210
19361
  * "precision": 4
19211
19362
  * }
19212
- * }```
19363
+ * }
19364
+ * ```
19213
19365
  */
19214
19366
  customUnits?: Record<string, object>;
19215
19367
  /**
@@ -19257,29 +19409,17 @@ declare namespace sap {
19257
19409
  */
19258
19410
  preserveDecimals?: boolean;
19259
19411
  /**
19260
- * Defines whether the unit of measure is shown in the formatted string, for example 1 day for locale "en"
19261
- *
19262
- * ```javascript
19263
- * NumberFormat.getUnitInstance({showMeasure: true})
19264
- * .format(1, "duration-day"); // "1 day"```
19265
- *
19266
- * ```javascript
19267
- * NumberFormat.getUnitInstance({showMeasure: false})
19268
- * .format(1, "duration-day"); // "1"```
19269
- * If both `showMeasure` and `showNumber` are set to false, an empty string is returned.
19412
+ * Defines whether the unit of measure is shown in the formatted string, for example, `1 day` for locale
19413
+ * `"en"`. `NumberFormat.getUnitInstance({showMeasure: true}).format(1, "duration-day"); // "1 day"` `NumberFormat.getUnitInstance({showMeasure:
19414
+ * false}).format(1, "duration-day"); // "1"` If both `showMeasure` and `showNumber` are set to false, an
19415
+ * empty string is returned.
19270
19416
  */
19271
19417
  showMeasure?: boolean;
19272
19418
  /**
19273
- * Defines whether the number is shown as part of the formatted string, for example 1 day for locale "en"
19274
- *
19275
- * ```javascript
19276
- * NumberFormat.getUnitInstance({showNumber: true})
19277
- * .format(1, "duration-day"); // "1 day"```
19278
- *
19279
- * ```javascript
19280
- * NumberFormat.getUnitInstance({showNumber: false})
19281
- * .format(1, "duration-day"); // "day"```
19282
- * If both `showMeasure` and `showNumber` are false, an empty string is returned
19419
+ * Defines whether the number is shown as part of the formatted string, for example, `1 day` for locale
19420
+ * `"en"`. `NumberFormat.getUnitInstance({showNumber: true}).format(1, "duration-day"); // "1 day"` `NumberFormat.getUnitInstance({showNumber:
19421
+ * false}).format(1, "duration-day"); // "day"` If both `showMeasure` and `showNumber` are false, an empty
19422
+ * string is returned.
19283
19423
  */
19284
19424
  showNumber?: boolean;
19285
19425
  /**
@@ -19322,92 +19462,7 @@ declare namespace sap {
19322
19462
  /**
19323
19463
  * Object which defines the format options
19324
19464
  */
19325
- oFormatOptions?: {
19326
- /**
19327
- * since 1.108.0 specifies the calendar week numbering. If specified, this overwrites `oFormatOptions.firstDayOfWeek`
19328
- * and `oFormatOptions.minimalDaysInFirstWeek`.
19329
- */
19330
- calendarWeekNumbering?: import("sap/base/i18n/date/CalendarWeekNumbering").default;
19331
- /**
19332
- * since 1.105.0 specifies the first day of the week starting with `0` (which is Sunday); if not defined,
19333
- * the value taken from the locale is used
19334
- */
19335
- firstDayOfWeek?: int;
19336
- /**
19337
- * since 1.105.0 minimal days at the beginning of the year which define the first calendar week; if not
19338
- * defined, the value taken from the locale is used
19339
- */
19340
- minimalDaysInFirstWeek?: int;
19341
- /**
19342
- * since 1.34.0 contains pattern symbols (e.g. "yMMMd" or "Hms") which will be converted into the pattern
19343
- * in the used locale, which matches the wanted symbols best. The symbols must be in canonical order, that
19344
- * 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),
19345
- * 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}.
19346
- */
19347
- format?: string;
19348
- /**
19349
- * a data pattern in LDML format. It is not verified whether the pattern represents only a date.
19350
- */
19351
- pattern?: string;
19352
- /**
19353
- * can be either 'short, 'medium', 'long' or 'full'. If no pattern is given, a locale dependent default
19354
- * date pattern of that style is used from the LocaleData class.
19355
- */
19356
- style?: string;
19357
- /**
19358
- * if true, by parsing it is checked if the value is a valid date
19359
- */
19360
- strictParsing?: boolean;
19361
- /**
19362
- * if true, the date is formatted relatively to todays date if it is within the given day range, e.g. "today",
19363
- * "1 day ago", "in 5 days"
19364
- */
19365
- relative?: boolean;
19366
- /**
19367
- * the day range used for relative formatting. If `oFormatOptions.relativeScale` is set to default value
19368
- * 'day', the relativeRange is by default [-6, 6], which means only the last 6 days, today and the next
19369
- * 6 days are formatted relatively. Otherwise when `oFormatOptions.relativeScale` is set to 'auto', all
19370
- * dates are formatted relatively.
19371
- */
19372
- relativeRange?: int[];
19373
- /**
19374
- * if 'auto' is set, new relative time format is switched on for all Date/Time Instances. The relative scale
19375
- * is chosen depending on the difference between the given date and now.
19376
- */
19377
- relativeScale?: string;
19378
- /**
19379
- * since 1.32.10, 1.34.4 the style of the relative format. The valid values are "wide", "short", "narrow"
19380
- */
19381
- relativeStyle?: string;
19382
- /**
19383
- * since 1.48.0 if true, the {@link sap.ui.core.format.DateFormat#format format} method expects an array
19384
- * with two dates as the first argument and formats them as interval. Further interval "Jan 10, 2008 - Jan
19385
- * 12, 2008" will be formatted as "Jan 10-12, 2008" if the 'format' option is set with necessary symbols.
19386
- * Otherwise the two given dates are formatted separately and concatenated with local dependent pattern.
19387
- */
19388
- interval?: boolean;
19389
- /**
19390
- * Since 1.113.0, a delimiter for intervals. With a given interval delimiter a specific interval format
19391
- * is created. **Example:** If `oFormatOptions.intervalDelimiter` is set to "...", an interval would be
19392
- * given as "Jan 10, 2008...Feb 12, 2008". **Note:** If this format option is set, the locale-specific interval
19393
- * notation is overruled, for example "Jan 10 – Feb 12, 2008" becomes "Jan 10, 2008...Feb 12, 2008".
19394
- */
19395
- intervalDelimiter?: string;
19396
- /**
19397
- * Only relevant if oFormatOptions.interval is set to 'true'. This allows to pass an array with only one
19398
- * date object to the {@link sap.ui.core.format.DateFormat#format format} method.
19399
- */
19400
- singleIntervalValue?: boolean;
19401
- /**
19402
- * if true, the date is formatted and parsed as UTC instead of the local timezone
19403
- */
19404
- UTC?: boolean;
19405
- /**
19406
- * The calender type which is used to format and parse the date. This value is by default either set in
19407
- * configuration or calculated based on current locale.
19408
- */
19409
- calendarType?: import("sap/base/i18n/date/CalendarType").default;
19410
- },
19465
+ oFormatOptions?: sap.ui.core.format.DateFormat.DateFormatOptions,
19411
19466
  /**
19412
19467
  * Locale to ask for locale specific texts/settings
19413
19468
  */
@@ -37925,6 +37980,30 @@ declare namespace sap {
37925
37980
  */
37926
37981
  sMimeType: string
37927
37982
  ): string;
37983
+ /**
37984
+ * Returns the HTML string for an icon URI.
37985
+ *
37986
+ * This method reuses the rendering logic from {@link sap.ui.core.RenderManager#icon} by calling it with
37987
+ * a lightweight DOM-building interface that mirrors the RenderManager's semantic API.
37988
+ *
37989
+ * @since 1.152
37990
+ *
37991
+ * @returns The HTML string for the icon, or empty string if the URI is not a valid icon URI
37992
+ */
37993
+ getIconHTML(
37994
+ /**
37995
+ * The icon URI (e.g. "sap-icon://accept")
37996
+ */
37997
+ sURI: sap.ui.core.URI,
37998
+ /**
37999
+ * Additional CSS classes to add to the icon element
38000
+ */
38001
+ aClasses?: string[],
38002
+ /**
38003
+ * Additional HTML attributes as key-value pairs
38004
+ */
38005
+ mAttributes?: object
38006
+ ): string;
37928
38007
  /**
37929
38008
  * Returns an info object for the icon with the given `iconName` and `collectionName`.
37930
38009
  *
@@ -48686,10 +48765,15 @@ declare namespace sap {
48686
48765
  */
48687
48766
  aClasses?: any[] | string,
48688
48767
  /**
48689
- * Additional attributes that will be added to the rendered tag. Currently the attributes `class` and `style`
48690
- * are not allowed
48768
+ * Additional attributes that will be added to the rendered tag. The attributes `class` and `style` are
48769
+ * not allowed. Use the `mStyles` parameter to set inline styles.
48691
48770
  */
48692
- mAttributes?: object
48771
+ mAttributes?: object,
48772
+ /**
48773
+ * A map of CSS property names and their values to be set as inline styles on the rendered tag. Example:
48774
+ * `{width: "16px", height: "16px"}`. This parameter is available since version 1.152.
48775
+ */
48776
+ mStyles?: object
48693
48777
  ): this;
48694
48778
  /**
48695
48779
  * Ends an open tag started with `openStart`.
@@ -56841,9 +56925,9 @@ declare namespace sap {
56841
56925
  */
56842
56926
  constructor(
56843
56927
  /**
56844
- * Format options as defined in {@link sap.ui.core.format.DateFormat.getDateInstance}
56928
+ * The format options
56845
56929
  */
56846
- oFormatOptions?: object,
56930
+ oFormatOptions?: sap.ui.core.format.DateFormat.DateFormatOptions,
56847
56931
  /**
56848
56932
  * constraints; {@link #validateValue validateValue} throws an error if any constraint is violated
56849
56933
  */
@@ -65226,6 +65310,110 @@ declare namespace sap {
65226
65310
  */
65227
65311
  sDateTimeOffset: string
65228
65312
  ): Date;
65313
+ /**
65314
+ * Parses a filter string to a syntax tree. In this tree:
65315
+ * Paths are leaves with `id="PATH"` and the path in `value`. Literals are leaves with `id="VALUE"`
65316
+ * and the literal (as parsed) in `value`. Operations are nodes with the operator in `id`, the operator
65317
+ * including the surrounding required space in `value`, and `left` and `right` containing syntax trees for
65318
+ * the operands. `not` only uses `right`. Functions are nodes with `id="FUNCTION"`, the name in `value`,
65319
+ * and an array of `parameters`. If the type is known (especially for logical operators and functions),
65320
+ * it is given in `type`. If a function parameter may have different types (like Edm.Decimal or Edm.Double
65321
+ * in `round`), it has the property `ambiguous: true`. `at` always contains the position where this token
65322
+ * started (starting with 1).
65323
+ *
65324
+ * Example: `parseFilter("foo eq 'bar' and length(baz) ne 5")` results in
65325
+ * ```javascript
65326
+ *
65327
+ * {
65328
+ * id : "and", value : " and ", type : "Edm.Boolean", at : 14,
65329
+ * left : {
65330
+ * id : "eq", value : " eq ", type : "Edm.Boolean", at : 5,
65331
+ * left : {id : "PATH", value : "foo", at : 1},
65332
+ * right : {id : "VALUE", value : "'bar'", at : 8}
65333
+ * },
65334
+ * right : {
65335
+ * id : "ne", value : " ne ", type : "Edm.Boolean", at : 30,
65336
+ * left : {
65337
+ * id : "FUNCTION", value : "length", type : "Edm.Int32", at : 18,
65338
+ * parameters : [{id : "PATH", value : "baz", at : 25}]
65339
+ * },
65340
+ * right : {id : "VALUE", value : "5", at : 33}
65341
+ * }
65342
+ * }
65343
+ * ```
65344
+ *
65345
+ *
65346
+ * @since 1.152.0
65347
+ *
65348
+ * @returns The syntax tree
65349
+ */
65350
+ parseFilter(
65351
+ /**
65352
+ * The filter string
65353
+ */
65354
+ sFilter: string
65355
+ ): object;
65356
+ /**
65357
+ * Parses a system query option "$select" or "$expand" into an object representation.
65358
+ *
65359
+ * The value for "$select" is an array of strings.
65360
+ *
65361
+ * The value for "$expand" is an object with the path as key and the options object as value. Each option
65362
+ * itself becomes a property with the option name as key and the option value as value. If there are no
65363
+ * options, the value for the path is `null`.
65364
+ *
65365
+ * If `bParseFilter` is set, the value for "$filter" is a syntax tree as described in {@link #.parseFilter};
65366
+ * otherwise it is the string passed to it.
65367
+ *
65368
+ * The value for all other options is the string passed to them.
65369
+ *
65370
+ * **Example:**
65371
+ *
65372
+ *
65373
+ * ```javascript
65374
+ *
65375
+ * sOption = "$expand=SO_2_BP,SO_2_SOITEM($expand=SOITEM_2_PRODUCT($expand=PRODUCT_2_BP"
65376
+ * + ";$select=ID,Name);$select=*;$count=true;$orderby=Name desc)"
65377
+ * ```
65378
+ * is converted to
65379
+ * ```javascript
65380
+ *
65381
+ * {
65382
+ * "$expand" : {
65383
+ * "SO_2_BP" : null,
65384
+ * "SO_2_SOITEM" : {
65385
+ * "$count" : "true",
65386
+ * "$expand" : {
65387
+ * "SOITEM_2_PRODUCT" : {
65388
+ * "$expand" : {
65389
+ * "PRODUCT_2_BP" : null
65390
+ * },
65391
+ * "$select" : ["ID", "Name"]
65392
+ * }
65393
+ * },
65394
+ * "$orderby" : "Name desc",
65395
+ * "$select" : ["*"]
65396
+ * }
65397
+ * }
65398
+ * }
65399
+ * ```
65400
+ *
65401
+ *
65402
+ * @since 1.152.0
65403
+ *
65404
+ * @returns The option as an object with the option name as key and the parsed value as value
65405
+ */
65406
+ parseSystemQueryOption(
65407
+ /**
65408
+ * The option string
65409
+ */
65410
+ sOption: string,
65411
+ /**
65412
+ * Whether to parse the value of "$filter" into a syntax tree as described in {@link #.parseFilter}; by
65413
+ * default, the value remains a string
65414
+ */
65415
+ bParseFilter?: boolean
65416
+ ): object;
65229
65417
  /**
65230
65418
  * Parses an "Edm.TimeOfDay" value and returns the corresponding JavaScript `Date` value (UTC with a date
65231
65419
  * value of "1970-01-01").
@@ -65305,6 +65493,8 @@ declare namespace sap {
65305
65493
  static getMetadata(): sap.ui.base.Metadata;
65306
65494
  /**
65307
65495
  * Collapses the group node that this context points to.
65496
+ *
65497
+ * **Note:** It is unsafe to keep a reference to a context instance which is not {@link #isKeepAlive kept alive}.
65308
65498
  * See:
65309
65499
  * #expand
65310
65500
  * #isExpanded
@@ -65368,7 +65558,7 @@ declare namespace sap {
65368
65558
  * Such a deletion is not a pending change.
65369
65559
  *
65370
65560
  * When using data aggregation without `groupLevels`, single entities can be deleted (since 1.151.0, see
65371
- * {@link #isAggregated}). The same restrictions as for a recursive hierarchy apply.
65561
+ * {@link #isAggregated}). The group ID must not have {@link sap.ui.model.odata.v4.SubmitMode.API}.
65372
65562
  * See:
65373
65563
  * #hasPendingChanges
65374
65564
  * #resetChanges
@@ -65499,7 +65689,9 @@ declare namespace sap {
65499
65689
  *
65500
65690
  * @returns The context's index within the binding's collection. It is `undefined` if
65501
65691
  * it does not belong to a list binding, it is {@link #isKeepAlive kept alive}, but not in the collection
65502
- * currently.
65692
+ * currently. When collapsing a node's ancestor in a recursive hierarchy, the index becomes `undefined`.
65693
+ * After expanding, the index is only determined again when that node comes into view, so to say. Use {@link sap.ui.model.odata.v4.ODataListBinding#getAllCurrentContexts }
65694
+ * to try to determine the index again.
65503
65695
  */
65504
65696
  getIndex(): number | undefined;
65505
65697
  /**
@@ -66530,7 +66722,9 @@ declare namespace sap {
66530
66722
  * Since 1.151.0, if the operation returns an "Edm.Stream" and the group ID '$stream' is used, the promise
66531
66723
  * resolves with a partial `Response` object containing only:
66532
66724
  * `body`: The response's `ReadableStream` `headers`: The response's `Headers` The promise
66533
- * rejects if '$stream' is used with a wrong return type.
66725
+ * rejects with an `Error` instance if '$stream' is used with a wrong return type or the fetch request fails.
66726
+ * In the latter case, the error contains the following properties:
66727
+ * `status`: {number} HTTP status code `statusText`: {string} (optional) HTTP status text
66534
66728
  */
66535
66729
  invoke(
66536
66730
  /**
@@ -68254,7 +68448,8 @@ declare namespace sap {
68254
68448
  /**
68255
68449
  * Type-specific format options, since 1.81.0. The boolean format option "parseKeepsEmptyString" applies
68256
68450
  * to {@link sap.ui.model.odata.type.String} only and is ignored for all other types. All other format options
68257
- * are passed "as is".
68451
+ * are passed "as is". Since 1.152.0, "parseKeepsEmptyString" is automatically set based on the model parameter
68452
+ * of the same name unless you provide `parseKeepsEmptyString: false` in `mFormatOptions`.
68258
68453
  */
68259
68454
  mFormatOptions?: object
68260
68455
  ): sap.ui.model.odata.type.ODataType;
@@ -68594,7 +68789,8 @@ declare namespace sap {
68594
68789
  /**
68595
68790
  * Type-specific format options, since 1.81.0. The boolean format option "parseKeepsEmptyString" applies
68596
68791
  * to {@link sap.ui.model.odata.type.String} only and is ignored for all other types. All other format options
68597
- * are passed "as is".
68792
+ * are passed "as is". Since 1.152.0, "parseKeepsEmptyString" is automatically set based on the model parameter
68793
+ * of the same name unless you provide `parseKeepsEmptyString: false` in `mFormatOptions`.
68598
68794
  */
68599
68795
  mFormatOptions?: object
68600
68796
  ): Promise<sap.ui.model.odata.type.ODataType>;
@@ -68830,6 +69026,13 @@ declare namespace sap {
68830
69026
  * is called.
68831
69027
  */
68832
69028
  operationMode?: sap.ui.model.odata.OperationMode;
69029
+ /**
69030
+ * Whether the format option `parseKeepsEmptyString` is set to `true` for all instances of {@link sap.ui.model.odata.type.String }
69031
+ * that are created automatically during type detection; only the value `true` is allowed; see {@link #getParseKeepsEmptyString}.
69032
+ *
69033
+ * @since 1.152.0
69034
+ */
69035
+ parseKeepsEmptyString?: boolean;
68833
69036
  /**
68834
69037
  * Root URL of the service to request data from. The path part of the URL must end with a forward slash
68835
69038
  * according to OData V4 specification ABNF, rule "serviceRoot". You may append OData custom query options
@@ -69629,6 +69832,19 @@ declare namespace sap {
69629
69832
  * @deprecated As of version 1.37.0. calling this method is not supported
69630
69833
  */
69631
69834
  getOriginalProperty(): void;
69835
+ /**
69836
+ * Returns whether the `parseKeepsEmptyString` format option is set to `true` for all instances of {@link sap.ui.model.odata.type.String }
69837
+ * that are created automatically during {@link sap.ui.model.odata.v4.ODataMetaModel#requestUI5Type type detection }
69838
+ * (as defined by the `parseKeepsEmptyString` model parameter, see {@link #constructor}). Use this model
69839
+ * setting if your OData service cannot handle `null` values for string properties.
69840
+ * See:
69841
+ * #constructor
69842
+ *
69843
+ * @since 1.152.0
69844
+ *
69845
+ * @returns Whether the `parseKeepsEmptyString` model parameter is set
69846
+ */
69847
+ getParseKeepsEmptyString(): boolean;
69632
69848
  /**
69633
69849
  * Method not supported
69634
69850
  * See:
@@ -69818,9 +70034,9 @@ declare namespace sap {
69818
70034
  * The handler is called with an `Error` having a property `retryAfter` of type `Date`, which is the earliest
69819
70035
  * point in time when the request should be repeated. The handler has to return a promise. With this promise,
69820
70036
  * you can control the repetition of all pending requests including the failed HTTP request. If the promise
69821
- * is resolved, the requests are repeated; if it is rejected, the requests are not repeated. If it is rejected
69822
- * with the same `Error` reason as previously passed to the handler, then this reason is reported to the
69823
- * message model.
70037
+ * is resolved, the requests are repeated; if it is rejected, the requests are not repeated but fail with
70038
+ * same reason as the promise. If the promise is rejected with the same `Error` reason as previously passed
70039
+ * to the handler, this reason is reported to the message model.
69824
70040
  *
69825
70041
  * @since 1.134.0
69826
70042
  */
@@ -75614,20 +75830,9 @@ declare namespace sap {
75614
75830
  */
75615
75831
  constructor(
75616
75832
  /**
75617
- * Formatting options. For a list of all available options, see {@link sap.ui.core.format.DateFormat.getDateInstance DateFormat}.
75833
+ * The format options
75618
75834
  */
75619
- oFormatOptions?: {
75620
- /**
75621
- * Additional set of options used to create a second `DateFormat` object for conversions between string
75622
- * values in the data source (e.g. model) and `Date`. This second format object is used to convert from
75623
- * a model `string` to `Date` before converting the `Date` to `string` with the primary format object. Vice
75624
- * versa, this 'source' format is also used to format an already parsed external value (e.g. user input)
75625
- * into the string format that is expected by the data source. For a list of all available options, see
75626
- * {@link sap.ui.core.format.DateFormat.getDateInstance DateFormat}. In case an empty object is given, the
75627
- * default is the ISO date notation (yyyy-MM-dd).
75628
- */
75629
- source?: object;
75630
- },
75835
+ oFormatOptions?: sap.ui.model.type.DateTypeFormatOptions,
75631
75836
  /**
75632
75837
  * Value constraints
75633
75838
  */
@@ -76724,6 +76929,24 @@ declare namespace sap {
76724
76929
  trailingCurrencyCode?: boolean;
76725
76930
  };
76726
76931
 
76932
+ /**
76933
+ * The format options for the `sap.ui.model.type.Date`.
76934
+ */
76935
+ type DateTypeFormatOptions =
76936
+ sap.ui.core.format.DateFormat.DateFormatOptions & {
76937
+ /**
76938
+ * Additional set of format options for a second `DateFormat` object. This object handles conversions between
76939
+ * string values in the data source (for example, model) and `Date` objects. These source options are used
76940
+ * for two-way data binding:
76941
+ * - **Model to View:** Converts a string from the model to a `Date` object. Afterwards the main format
76942
+ * options are used to convert that `Date` object to a string for display.
76943
+ * - **View to Model:** Converts a parsed external value, for example, user input, into the string format
76944
+ * that the data source requires. If an empty object is provided, the default format is the ISO date
76945
+ * notation (yyyy-MM-dd).
76946
+ */
76947
+ source?: sap.ui.core.format.DateFormat.DateFormatOptions;
76948
+ };
76949
+
76727
76950
  /**
76728
76951
  * The format options of the {@link sap.ui.model.type.Float} type.
76729
76952
  */
@@ -88719,6 +88942,12 @@ declare namespace sap {
88719
88942
 
88720
88943
  "sap/ui/core/Placeholder": undefined;
88721
88944
 
88945
+ "sap/ui/core/popover/PopoverFlipMode": undefined;
88946
+
88947
+ "sap/ui/core/popover/PopoverPhysicalSide": undefined;
88948
+
88949
+ "sap/ui/core/popover/Positioning": undefined;
88950
+
88722
88951
  "sap/ui/core/Popup": undefined;
88723
88952
 
88724
88953
  "sap/ui/core/postmessage/Bus": undefined;
@@ -89175,6 +89404,8 @@ declare namespace sap {
89175
89404
 
89176
89405
  "sap/ui/model/xml/XMLTreeBinding": undefined;
89177
89406
 
89407
+ "sap/ui/performance/FetchInterceptor": undefined;
89408
+
89178
89409
  "sap/ui/performance/Measurement": undefined;
89179
89410
 
89180
89411
  "sap/ui/performance/trace/FESR": undefined;