@sapui5/ts-types 1.104.1 → 1.105.1

package/types/sap.uiext.inbox.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.0
 
 declare namespace sap {
   namespace uiext {

package/types/sap.ushell.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.1
 
 declare namespace sap {
   namespace ushell {
@@ -850,7 +850,7 @@ declare namespace sap {
        * of the currently running app (but still in scope of the current Fiori launchpad) or create links to such
        * external targets.
        *
-       * To use the CrossApplicationNavigation service you can retrive an instance via ushell's Container:
+       * To use the CrossApplicationNavigation service you can retrieve an instance via ushell's Container:
        * ```javascript
        *
        * sap.ushell.Container.getServiceAsync("CrossApplicationNavigation").then(function (CrossApplicationNavigationService) {
@@ -1016,7 +1016,7 @@ declare namespace sap {
            *                               // Possible values are:
            *                               //   - "intent" (default) lexicographical sort on returned 'intent' field
            *                               //   - "text" lexicographical sort on returned 'text' field
-           *                               //   - "priority" exprimental - top intents are returned first
+           *                               //   - "priority" experimental - top intents are returned first
            *
            *      treatTechHintAsFilter : true, // optional, defaults to false
            *                                    // if true, only apps that match
@@ -1603,7 +1603,7 @@ declare namespace sap {
         toExternal(
           /**
            * A configuration object describing the navigation target. The navigation target can be provided as its
-           * separate aspects like semantic object, action, paramters etc. in separate members of the configuration
+           * separate aspects like semantic object, action, parameters etc. in separate members of the configuration
            * object.
            *
            * **Note:** Parameter values can contain special characters and must be provided unencoded; the function
@@ -1656,7 +1656,7 @@ declare namespace sap {
            *
            *
            * Alternatively a `shellHash` can be provided that includes already all aspects of the navigation target:
-           * semantic object, action, intent paramters, app-specific route (incuding app paramters)
+           * semantic object, action, intent parameters, app-specific route (including app parameters)
            *
            * **Note:** While parameters need to be url-encoded once when used in the `shellHash` the app specific
            * route must not be encoded.
@@ -1675,7 +1675,7 @@ declare namespace sap {
            * To navigate to the homepage of the Fiori launchpad, navigate to `{target: {shellHash: "#"}}`. Do not
            * use "#Shell-home" or "Shell-home" to navigate to!
            *
-           * To provide a complex paramter structure to a target app the pesudo parameter `sap-xapp-state-data` can
+           * To provide a complex parameter structure to a target app the pseudo parameter `sap-xapp-state-data` can
            * be used.
            *
            * Example:
@@ -11440,8 +11440,6 @@ declare namespace sap {
 
     "sap/ushell/services/LaunchPage": undefined;
 
-    "sap/ushell/services/Menu": undefined;
-
     "sap/ushell/services/Message": undefined;
 
     "sap/ushell/services/NavTargetResolution": undefined;

package/types/sap.ushell_abap.d.ts

@@ -1,221 +1,7 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.1
 
 declare namespace sap {
-  namespace ui {
-    /**
-     * Provides access to UI5 loader configuration.
-     *
-     * The configuration is used by {@link sap.ui.require} and {@link sap.ui.define}.
-     */
-    namespace loader {
-      /**
-       * @SINCE 1.56.0
-       *
-       * Sets the configuration for the UI5 loader. The configuration can be updated multiple times. Later changes
-       * do not impact modules that have been loaded before.
-       *
-       * If no parameter is given, a partial copy of UI5 loader configuration in use is returned.
-       *
-       * The configuration options are aligned with the "Common Config" draft of the AMD spec (https://github.com/amdjs/amdjs-api/blob/master/CommonConfig.md).
-       *
-       * The following code shows an example of what a UI5 loader configuration might look like:
-       * ```javascript
-       *
-       *
-       *   sap.ui.loader.config({
-       *
-       *     // location from where to load all modules by default
-       *     baseUrl: '../../resources/',
-       *
-       *     paths: {
-       *       // load modules whose ID equals to or starts with 'my/module' from example.com
-       *       'my/module': 'https://example.com/resources/my/module'
-       *     },
-       *
-       *     map: {
-       *       // if any module requires 'sinon', load module 'sap/ui/thirdparty/sinon-4'
-       *       '*': {
-       *         'sinon': 'sap/ui/thirdparty/sinon-4'
-       *       },
-       *       // but if a module whose ID equals to or starts with 'app' requires 'sinon'
-       *       // then load a legacy version instead
-       *       "app": {
-       *         'sinon': 'sap/ui/legacy/sinon'
-       *       }
-       *     },
-       *
-       *     // define two bundles that consists of JS modules only
-       *     bundles: {
-       *       bundle1: ['module1', 'module2'],
-       *       bundle2: ['moduleX', 'moduleY']
-       *     },
-       *
-       *     // define a bundle that also contains non-JS resources
-       *     bundlesUI5: {
-       *       'all.js': ['Component.js', 'manifest.json',
-       *                  'App.controller.js', 'App.view.xml']
-       *     },
-       *
-       *     // activate real async loading and module definitions
-       *     async: true,
-       *
-       *     // provide dependency and export metadata for non-UI5 modules
-       *     shim: {
-       *       'sap/ui/thirdparty/blanket': {
-       *         amd: true,
-       *         exports: 'blanket'
-       *       }
-       *     }
-       *
-       *   });
-       *
-       * ```
-       *
-       *
-       * @returns UI5 loader configuration in use.
-       */
-      function config(
-        /**
-         * The provided configuration gets merged with the UI5 loader configuration in use. If `cfg` is omitted
-         * or `undefined`, a copy of the current configuration gets returned, containing at least the properties
-         * `amd` and `async`.
-         */
-        cfg?: {
-          /**
-           * Default location to load modules from. If none of the configured `paths` prefixes matches a module ID,
-           * the module will be loaded from the concatenation of the `baseUrl` and the module ID.
-           *
-           * If the `baseUrl` itself is a relative URL, it is evaluated relative to `document.baseURI`.
-           */
-          baseUrl?: string;
-          /**
-           * A map of resource locations keyed by a corresponding module ID prefix. When a module is to be loaded,
-           * the longest key in `paths` is searched that is a prefix of the module ID. The module will be loaded from
-           * the concatenation of the corresponding value in `paths` and the remainder of the module ID (after the
-           * prefix). If no entry in `paths` matches, then the module will be loaded from the `baseUrl`.
-           *
-           * The prefixes (keys) must not contain relative segments (./ or ../), a trailing slash will be removed,
-           * and only full name segment matches are considered a match (prefix 'sap/m' does not match a module ID
-           * 'sap/main').
-           *
-           * **Note**: In contrast to the "Common Config" of the AMD spec, the paths (values in the map) are interpreted
-           * relative to `document.baseURI`, not relative to `cfg.baseUrl`.
-           */
-          paths?: Record<string, string>;
-          /**
-           * A map of maps that defines how to map module IDs to other module IDs (inner maps) in the context of a
-           * specific set of modules (keys of outer map).
-           *
-           * Each key of the outer map represents a module ID prefix that describes the context for which its value
-           * (inner map) has to be used. The special key `*` describes the default context which applies for any module.
-           * Only the most specific matching context will be taken into account.
-           *
-           * Each inner map maps a module ID or module ID prefix to another module ID or module ID prefix. Again,
-           * only the most specific match is taken into account and only one mapping is evaluated (the evaluation
-           * of the mappings is not done recursively).
-           *
-           * Matches are always complete matches, a prefix 'a/b/c' does not match the module ID 'a/b/com'.
-           */
-          map?: Record<string, Record<string, string>>;
-          /**
-           * Defines additional metadata for modules for which the normal behavior of the AMD APIs is not sufficient.
-           *
-           * A typical example are scripts that don't use `define` or `sap.ui.define`, but export to a global name.
-           * With the `exports` property, one or more export names can be specified, and the loader can retrieve the
-           * exported value after executing the corresponding module. If such a module has dependencies, they can
-           * be specified in the `deps` array and are loaded and executed before executing the module.
-           *
-           * The `amd` flag of a shim is a ui5loader-specific extension of the standard AMD shims. If set, the ui5loader
-           * hides a currently active AMD loader before executing the module and restores it afterwards. Otherwise,
-           * it might miss the export of third party modules that check for an AMD loader and register with it instead
-           * of exporting to a global name. A future version of the ui5loader might ignore this flag when it acts
-           * as an AMD loader by itself.
-           *
-           * **Note:** The ui5loader does not support the `init` option described by the "Common Config" section of
-           * the AMD spec.
-           */
-          shim?: Record<
-            string,
-            {
-              amd: boolean;
-
-              deps: string[];
-
-              exports: string | string[];
-            }
-          >;
-          /**
-           * A map of arrays that each define the modules contained in a bundle.
-           *
-           * Each key of the map represents the module ID of a bundle file. The array value represents the set of
-           * JavaScript modules (their module IDs) that are contained in the bundle.
-           *
-           * When a module is required that has not been loaded yet, and for which a containing bundle is known, that
-           * bundle will be required first. Only then the original module will be required again and usually be taken
-           * from the just loaded bundle.
-           *
-           * A bundle will be loaded asynchronously only when the loader is in asynchronous mode and when the request
-           * for the contained module originates from an asynchronous API. In all other cases, the bundle has to be
-           * loaded synchronously to fulfill API contracts.
-           *
-           * **Note:** The loader only supports one containing bundle per module. If a module is declared to be part
-           * of multiple bundles, only the last one will be taken into account.
-           *
-           * This configuration option is basically provided to be compatible with requireJS or SystemJS configuration.
-           */
-          bundles?: Record<string, string[]>;
-          /**
-           * A map of arrays that each define the resources contained in a bundle.
-           *
-           * This is similar to `bundles`, but all strings are unified resource names including a file type extension,
-           * not only module IDs. This allows to represent more than just JavaScript modules.
-           *
-           * Each key of the map represents the resource name (in unified resource name syntax) of a bundle file.
-           * The array value represents the set of resources (also in unified resource name syntax) that are contained
-           * in the bundle. The array can contain JavaScript as well as other textual resource types (e.g. *.xml or
-           * *.json resources).
-           *
-           * When a module is required that has not been loaded yet, and for which a containing bundle is known, that
-           * bundle will be required first. Only then the original module will be required again and usually be taken
-           * from the just loaded bundle.
-           *
-           * A bundle will be loaded asynchronously only when the loader is in asynchronous mode and when the request
-           * for the contained module originates from an asynchronous API. In all other cases, the bundle has to be
-           * loaded synchronously to fulfill API contracts.
-           *
-           * **Note:** The loader only supports one containing bundle per module. If a module is declared to be part
-           * of multiple bundles, only the last one will be taken into account.
-           *
-           * **Note:** Although non-JS resources can be declared to be part of a bundle, only requests for JavaScript
-           * modules will currently trigger the loading of a bundle.
-           */
-          bundlesUI5?: Record<string, string[]>;
-          /**
-           * When set to true, `sap.ui.require` loads modules asynchronously via script tags and `sap.ui.define` executes
-           * asynchronously. To enable this feature, it is recommended to set the attribute `data-sap-ui-async="true"`
-           * on the application bootstrap tag.
-           *
-           * **Note:** Switching back from async to sync is not supported and trying to do so will throw an `Error`
-           */
-          async?: boolean;
-          /**
-           * When set to true, the ui5loader will overwrite the global properties `define` and `require` with its
-           * own implementations. Any previously active AMD loader will be remembered internally and can be restored
-           * by setting `amd` to false again.
-           *
-           * **Note:** Switching to the `amd` mode, the ui5loader will set `async` to true implicitly for activating
-           * asynchronous loading. Once the loading behaviour has been defined to be asynchronous, it can not be changed
-           * to synchronous behaviour again, also not via setting `amd` to false.
-           */
-          amd?: boolean;
-        }
-      ): object | undefined;
-    }
-  }
-
   interface IUI5DefineDependencyNames {
-    "sap/ushell_abap/bootstrap/evo/abap-dbg": undefined;
-
     "sap/ushell_abap/library": undefined;
   }
 }

package/types/sap.uxap.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.0
 
 declare namespace sap {
   /**

package/types/sap.viz.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.0
 
 declare namespace sap {
   /**

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

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

package/types/sap.zen.commons.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.0
 
 declare namespace sap {
   namespace zen {

package/types/sap.zen.crosstab.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.0
 
 declare namespace sap {
   namespace zen {

package/types/sap.zen.dsh.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.104.0
+// For Library Version: 1.105.0
 
 declare namespace sap {
   namespace zen {