New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@openui5/ts-types

Package Overview
Dependencies
Maintainers
5
Versions
250
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@openui5/ts-types - npm Package Compare versions

Comparing version 1.64.1 to 1.65.0

4

CHANGELOG.md

@@ -0,1 +1,5 @@

## 1.65.0
Update to OpenUI5 1.65.1
## 1.64.1

@@ -2,0 +6,0 @@

10

package.json
{
"name": "@openui5/ts-types",
"description": "OpenUI5 TypeScript Definitions",
"version": "1.64.1",
"version": "1.65.0",
"license": "Apache-2.0",
"types": "types/sap.ui.core.d.ts",
"openUI5Version": "1.64.1",
"openUI5Version": "1.65.1",
"devDependencies": {
"@ui5/cli": "1.3.0",
"@ui5/dts-generator": "^1.64.0",
"@ui5/cli": "1.4.2",
"@ui5/dts-generator": "^1.65.0",
"fs-extra": "^7.0.1",

@@ -26,3 +26,3 @@ "klaw-sync": "^6.0.0",

},
"gitHead": "298e8065660d84faef303adcf436e9c4e760021a"
"gitHead": "061f09d4a114f72e077a46fc9a180c87a4e48bed"
}

@@ -1,2 +0,2 @@

![npm (scoped)](https://img.shields.io/npm/v/@openui5/ts-types.svg)
[![npm (scoped)](https://img.shields.io/npm/v/@openui5/ts-types.svg)](https://www.npmjs.com/package/@openui5/ts-types)

@@ -24,3 +24,4 @@ # @openui5/ts-types

- [Runnable Demo Package](../../demos/demo-js)
- [Runnable JavaScript Demo Package](../../demos/demo-js)
- [Runnable TypeScript Demo Package](../../demos/demo-ts)

@@ -40,7 +41,7 @@ ## Prerequisites

- `npm install @openui5/ts-types --dev`
- `npm install @openui5/ts-types --save-dev`
It is recommended to align with the specific OpenUI5 version you may be using, e.g for OpenUI5 1.64:
- `npm install @openui5/ts-types@1.64 --dev`
- `npm install @openui5/ts-types@1.64 --save-dev`

@@ -47,0 +48,0 @@ Note that the version matching is only for the major and minor versions.

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -582,3 +582,3 @@ declare namespace sap {

*/
getAriaDescribedBy(): sap.ui.core.ID[];
getAriaDescribedBy(): any;
/**

@@ -588,3 +588,3 @@ * Returns array of IDs of the elements which are the current targets of the association {@link #getAriaLabelledBy

*/
getAriaLabelledBy(): sap.ui.core.ID[];
getAriaLabelledBy(): any;
/**

@@ -603,3 +603,3 @@ * Gets current value of property {@link #getExpanded expanded}.

*/
getItems(): sap.tnt.NavigationListItem[];
getItems(): any;
/**

@@ -656,7 +656,7 @@ * Returns a metadata object for class sap.tnt.NavigationList.

*/
removeAllAriaDescribedBy(): sap.ui.core.ID[];
removeAllAriaDescribedBy(): any;
/**
* Removes all the controls in the association named {@link #getAriaLabelledBy ariaLabelledBy}.
*/
removeAllAriaLabelledBy(): sap.ui.core.ID[];
removeAllAriaLabelledBy(): any;
/**

@@ -667,3 +667,3 @@ * Removes all the controls from the aggregation {@link #getItems items}.

*/
removeAllItems(): sap.tnt.NavigationListItem[];
removeAllItems(): any;
/**

@@ -901,3 +901,3 @@ * Removes an ariaDescribedBy from the association named {@link #getAriaDescribedBy ariaDescribedBy}.

*/
getItems(): sap.tnt.NavigationListItem[];
getItems(): any;
/**

@@ -948,3 +948,3 @@ * Returns a metadata object for class sap.tnt.NavigationListItem.

*/
removeAllItems(): sap.tnt.NavigationListItem[];
removeAllItems(): any;
/**

@@ -1300,2 +1300,18 @@ * Removes a item from the aggregation {@link #getItems items}.

* - The app menu and the side navigation must not have any dependencies and must work independently.
* Fiori 3 theme specifics: In Fiori 3 Default theme the ToolHeader is with dark design unlike most
* of the other controls. This defines the usage of limited controls inside it, which will result in good
* design combination.
* The ToolHeader stylizes the contained controls with the Shell color parameters, to match the dark design
* requirement. However, that's not a dark theme.
*
* Only the following controls are supported:
* - sap.m.Text
* - sap.m.Title
* - sap.m.ObjectStatus
* - sap.ui.core.Icon
* - sap.m.Button
* - sap.m.MenuButton
* - sap.m.Select
* - sap.m.SearchField
* - sap.m.IconTabHeader
*/

@@ -1482,3 +1498,3 @@ class ToolHeader extends sap.m.OverflowToolbar {

*/
getMainContents(): sap.ui.core.Control[];
getMainContents(): any;
/**

@@ -1533,3 +1549,3 @@ * Returns a metadata object for class sap.tnt.ToolPage.

*/
removeAllMainContents(): sap.ui.core.Control[];
removeAllMainContents(): any;
/**

@@ -1536,0 +1552,0 @@ * Removes a mainContent from the aggregation {@link #getMainContents mainContents}.

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -27,0 +27,0 @@ declare namespace sap {

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -27,0 +27,0 @@ declare namespace sap {

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -27,0 +27,0 @@ declare namespace sap {

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -27,0 +27,0 @@ declare namespace sap {

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -27,0 +27,0 @@ declare namespace sap {

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -41,2 +41,9 @@ declare namespace sap {

/**
* @EXPERIMENTAL (since 1.65)
*
* The parameters used in the manifest.
*/
parameters?: object;
/**
* Defines the width of the card.

@@ -52,2 +59,10 @@ */

/**
* @SINCE 1.65
* @EXPERIMENTAL (since 1.65)
*
* Defines the state of the `Card`. When set to `Inactive`, the `Card` doesn't make requests.
*/
dataMode?: sap.ui.integration.CardDataMode;
/**
* @EXPERIMENTAL (since 1.64)

@@ -70,15 +85,15 @@ *

* Overview: Cards are small user interface elements which provide the most important information from an
* application related to a specific role or task in a compact manner allowing for actions to be executed.
* Cards can be described as small representations of an application which can be integrated in different
* systems.
* app, related to a specific role or task. The information is represented in a compact manner, allowing
* for actions to be executed. Cards can be described as small representations of an app which can be integrated
* in different systems.
*
* The integration card is defined in a declarative way by using a manifest.json allowing it to:
* - Be easily integrated in an applications
* - Be easily reused across different applications.
* - Be easily understandable by other technologies.
* - Be self-contained. No need for external configuration.
* - Be easily reconfigured in different application layers (including backend).
* - Separate the roles of the card developer and the application developer.
* The integration card is defined in a declarative way, using a manifest.json to be:
* - Easily integrated into apps
* - Easily reused across apps
* - Understandable by other technologies
* - Self-contained (without external configuration)
* - Easily reconfigured in app layers (including backend)
* - Easy to separate the roles of the card and the app developers
*
* Card developer role - Describe the card in a manifest.json defining:
* The role of the card developer is to describe the card in a manifest.json file and define:
* - Header

@@ -89,12 +104,13 @@ * - Content

*
* Application developer role - Integrate the card into an application defining:
* - Dimensions of the card inside a layout of choice, using the width and height properties.
* - Behavior for the described actions in the manifest.json, using the action event.
* The role of the app developer is to integrate the card into the app and define:
* - The dimensions of the card inside a layout of choice, using the `width` and `height` properties
* - The behavior for the actions described in the manifest.json file, using the action event
*
* Usage:
*
* The "sap.app" type property of the manifest have to be set to "card". The namespace used to define a
* card is "sap.card". Every card have a type. Which can be one of: List, Analytical, Timeline, Object.
* The `"sap.app"` `type` property in the manifest file must be set to `"card"`. The namespace used to define
* a card is `"sap.card"`. Every card has a type which can be one of the following: List, Analytical, Timeline,
* Object, Table, Component (experimental)
*
* Example manifest.json:
* An example of a manifest.json:
*

@@ -125,3 +141,3 @@ *

*
* The default header type can contain title, subtitle, icon and status.
* The default header type can contain title, subtitle, icon, and status.
* ```javascript

@@ -150,4 +166,4 @@ *

*
* The numeric header type can contain title, subtitle, unitOfMeasurement, details, main indicator and side
* indicators.
* The numeric header type can contain title, subtitle, unitOfMeasurement, details, main indicator, and
* side indicators.
* ```javascript

@@ -196,5 +212,9 @@ *

* - Analytical
* - Table
* - Component (experimental)
*
* List card contains a set of items. "item" property defines the template for all the items of the list.
* "data" property provides the data. Example:
* List card contains a set of items. The `"item"` property defines the template for all the items of the
* list. The `"data"` property provides the displayed information.
*
* Example:
* ```javascript

@@ -215,3 +235,3 @@ *

* "Name": "Comfort Easy",
* "Description": "32 GB Digital Assistant with high-resolution color screen",
* "Description": "A 32 GB Digital Assistant with a high-resolution color screen",
* "Highlight": "Error"

@@ -221,3 +241,3 @@ * },

* "Name": "ITelO Vault",
* "Description": "Digital Organizer with State-of-the-Art Storage Encryption",
* "Description": "A Digital Organizer with state-of-the-art Storage Encryption",
* "Highlight": "Warning"

@@ -250,3 +270,5 @@ * },

* Analytical card contains a chart visualization configuration. Supported chart types are Line, StackedBar,
* StackedColumn, Donut. Example:
* StackedColumn, Donut.
*
* Example:
* ```javascript

@@ -340,3 +362,5 @@ *

* Object card contains information about an object. It is structured in groups. Every group can have a
* title and items. The items contain display name (label) and value. Example:
* title and items. The items contain display name (label) and value.
*
* Example:
* ```javascript

@@ -393,4 +417,6 @@ *

*
* Timeline card contains a set of timeline items. "item" property defines the template for all the items
* of the timeline. Example:
* Timeline card contains a set of timeline items. The "item" property defines the template for all the
* items of the timeline.
*
* Example:
* ```javascript

@@ -450,9 +476,120 @@ *

*
* Item based cards (Timeline and List) have an additional content property "maxItems" which defines the
* maximum number of items the card can have.
* Table card displays a set of items in a table format. The `"row"` property defines the template for all
* rows of the table.
*
* Data handling: In order to add data to the card you can add a data section to the card, header or content.
* The card will automatically create an unnamed model which then can be used to resolve binding syntaxes
* inside the card manifest.
* Example:
* ```javascript
*
*
* {
* "sap.app": {
* "type": "card"
* },
* "sap.card": {
* "type": "Table",
* "header": {
* ...
* },
* "content": {
* "data": {
* "json": [
* {
* "salesOrder": "5000010050",
* "customerName": "Robert Brown Entertainment",
* "netAmount": "2K USD",
* "status": "Delivered",
* "statusState": "Success"
* },
* {
* "salesOrder": "5000010051",
* "customerName": "Entertainment Argentinia",
* "netAmount": "127k USD",
* "status": "Canceled",
* "statusState": "Error"
* },
* {
* "salesOrder": "5000010052",
* "customerName": "Brazil Technologies",
* "netAmount": "8K USD",
* "status": "In Progress",
* "statusState": "Warning"
* }
* ]
* },
* "row": {
* "columns": [{
* "title": "Sales Order",
* "value": "{salesOrder}",
* "identifier": true
* },
* {
* "title": "Customer",
* "value": "{customerName}"
* },
* {
* "title": "Net Amount",
* "value": "{netAmount}"
* },
* {
* "title": "Status",
* "value": "{status}",
* "state": "{statusState}"
* }
* ]
* }
* }
* }
* }
*
* ```
*
*
* Component card can be used to display multiple controls (inside one Component). It is used as a custom
* approach for use cases, which do not fit in other card types and structures. It provides much more flexibility
* and responsibility to the Card’s authors. Reusability is achieved on Component level and this type of
* Card is usable in LOB products that are based on the SAPUI5 Framework.
*
* Example:
* ```javascript
*
*
* {
* "sap.app": {
* "id": "sap.ui.integration.sample.ComponentCard.cardContent",
* "type": "card",
* "applicationVersion": {
* "version": "1.0.0"
* }
* },
* "sap.ui5": {
* "rootView": {
* "viewName": "sap.ui.integration.sample.ComponentCard.cardContent.View",
* "type": "XML",
* "async": true,
* "id": "app"
* },
* "dependencies": {
* "minUI5Version": "1.38",
* "libs": {
* "sap.m": {}
* }
* }
* },
* "sap.card": {
* "type": "Component",
* "header": {
* "title": "Visit our workshop"
* }
* }
* }
*
* ```
*
*
* Item-based cards (Timeline and List) have an additional `"maxItems"` content property, which defines
* the maximum number of items the card can have.
*
* Data Handling: To add data to the card, you can add a data section, header or content. The card automatically
* creates an unnamed model which can be used to resolve binding syntaxes inside the card manifest.
*
* Static data:

@@ -510,4 +647,6 @@ * ```javascript

*
* Actions: Actions adds behavior to the card. To add a navigation action to the header and to the items
* you can configure it inside the manifest. Actions have:
* Actions: Actions add behavior to the card. To add a navigation action to the header and to the items,
* you can configure it inside the manifest.
*
* Actions have:
* - Type

@@ -517,3 +656,3 @@ * - Parameters

*
* In the example below navigation action is added both to the header and the list items:
* In the example below, a navigation action is added both to the header and the list items:
* ```javascript

@@ -579,11 +718,11 @@ *

* When to use
* - When the card have to be reused across applications.
* - When easy integration and configuration is needed.
* - When you want to reuse the card across apps.
* - When you need easy integration and configuration.
*
* When not to use
* - When more header and content flexibility is needed.
* - When you need more header and content flexibility.
* - When you have to achieve simple card visualization. For such cases, use: {@link sap.f.Card Card}.
*
* - When an application model have to be used. For such cases, use: {@link sap.f.Card Card}.
* - When complex behavior is needed. For such cases, use: {@link sap.f.Card Card}.
* - When you have to use an application model. For such cases, use: {@link sap.f.Card Card}.
* - When you need complex behavior. For such cases, use: {@link sap.f.Card Card}.
*/

@@ -597,2 +736,4 @@ class Card extends sap.ui.core.Control implements sap.f.ICard {

* of the syntax of the settings object.
* See:
* {@link topic:5b46b03f024542ba802d99d67bc1a3f4 Cards}
*/

@@ -706,2 +847,17 @@ constructor(

/**
* Implements sap.f.ICard interface.
*/
getCardHeaderPosition(): any;
/**
* @SINCE 1.65
* @EXPERIMENTAL (since 1.65)
*
* Gets current value of property {@link #getDataMode dataMode}.
*
* Defines the state of the `Card`. When set to `Inactive`, the `Card` doesn't make requests.
*
* Default value is `Active`.
*/
getDataMode(): sap.ui.integration.CardDataMode;
/**
* Gets current value of property {@link #getHeight height}.

@@ -720,9 +876,5 @@ *

/**
* Gets current value of property {@link #getManifest manifest}.
*
* The URL of the manifest or an object.
*
* Default value is `empty string`.
* Overwrites getter for card manifest.
*/
getManifest(): any;
getManifest(): string | Object;
/**

@@ -734,2 +886,6 @@ * Returns a metadata object for class sap.ui.integration.widgets.Card.

/**
* Overwrites getter for card parameters.
*/
getParameters(): Object;
/**
* Gets current value of property {@link #getWidth width}.

@@ -743,2 +899,24 @@ *

/**
* @EXPERIMENTAL (since 1.65)
*/
isReady(): boolean;
/**
* @EXPERIMENTAL (since 1.65)
*
* Refreshes the card by re-applying the manifest settings and triggering all data requests.
*/
refresh(): void;
/**
* @SINCE 1.65
* @EXPERIMENTAL (since 1.65)
*
* Sets a new value for the `dataMode` property.
*/
setDataMode(
/**
* The mode to set to the Card.
*/
sMode: sap.ui.integration.CardDataMode
): sap.ui.integration.widgets.Card;
/**
* Sets a new value for property {@link #getHeight height}.

@@ -769,3 +947,3 @@ *

/**
* Setter for card manifest.
* Overwrites setter for card manifest.
*/

@@ -779,2 +957,11 @@ setManifest(

/**
* Overwrites setter for card params.
*/
setParameters(
/**
* oParameters Parameters set in the card trough parameters property.
*/
vValue: Object
): sap.ui.integration.widgets.Card;
/**
* Sets a new value for property {@link #getWidth width}.

@@ -816,2 +1003,19 @@ *

}
/**
* @SINCE 1.65
* @EXPERIMENTAL (since 1.65)
*
* Possible data modes for `{@link sap.ui.integration.widgets.Card}`.
*/
enum CardDataMode {
/**
* When in this mode, the card can make requests.
*/
Active,
/**
* When in this mode, the card cannot make requests.
*/
Inactive
}
}

@@ -818,0 +1022,0 @@ }

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -27,0 +27,0 @@ declare namespace sap {

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -212,3 +212,3 @@ declare namespace sap {

*/
getAriaDescribedBy(): sap.ui.core.ID[];
getAriaDescribedBy(): any;
/**

@@ -218,3 +218,3 @@ * Returns array of IDs of the elements which are the current targets of the association {@link #getAriaLabelledBy

*/
getAriaLabelledBy(): sap.ui.core.ID[];
getAriaLabelledBy(): any;
/**

@@ -261,7 +261,7 @@ * Gets current value of property {@link #getColor color}.

*/
removeAllAriaDescribedBy(): sap.ui.core.ID[];
removeAllAriaDescribedBy(): any;
/**
* Removes all the controls in the association named {@link #getAriaLabelledBy ariaLabelledBy}.
*/
removeAllAriaLabelledBy(): sap.ui.core.ID[];
removeAllAriaLabelledBy(): any;
/**

@@ -486,3 +486,3 @@ * Removes an ariaDescribedBy from the association named {@link #getAriaDescribedBy ariaDescribedBy}.

*/
getAriaDescribedBy(): sap.ui.core.ID[];
getAriaDescribedBy(): any;
/**

@@ -492,3 +492,3 @@ * Returns array of IDs of the elements which are the current targets of the association {@link #getAriaLabelledBy

*/
getAriaLabelledBy(): sap.ui.core.ID[];
getAriaLabelledBy(): any;
/**

@@ -509,7 +509,7 @@ * Returns a metadata object for class sap.ui.suite.VerticalProgressIndicator.

*/
removeAllAriaDescribedBy(): sap.ui.core.ID[];
removeAllAriaDescribedBy(): any;
/**
* Removes all the controls in the association named {@link #getAriaLabelledBy ariaLabelledBy}.
*/
removeAllAriaLabelledBy(): sap.ui.core.ID[];
removeAllAriaLabelledBy(): any;
/**

@@ -516,0 +516,0 @@ * Removes an ariaDescribedBy from the association named {@link #getAriaDescribedBy ariaDescribedBy}.

@@ -24,3 +24,3 @@ /**

/// <reference path="./sap.uxap.d.ts" />
// For Library Version: 1.64.1
// For Library Version: 1.65.1

@@ -95,3 +95,3 @@ declare namespace sap {

*/
components?: string[];
components?: any;
},

@@ -159,3 +159,3 @@ /**

*/
aLibraries: Object[]
aLibraries: any
): void;

@@ -178,3 +178,3 @@ /**

*/
aLibraries: Object[]
aLibraries: any
): void;

@@ -181,0 +181,0 @@ /**

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc