@openui5/types 1.115.1 → 1.116.0

package/README.md

@@ -20,18 +20,19 @@ These capabilities are available not only for OpenUI5 apps written in TypeScript
 
 The central entry point for all information about using UI5 with TypeScript (incl. sample apps and templates) is https://sap.github.io/ui5-typescript.
 
+The [UI5 TypeScript tutorial](https://github.com/SAP-samples/ui5-typescript-tutorial) gives the best end-to-end impression of UI5 application and control development in TypeScript. The above and below links lead to further details about certain aspects.
+
 To see the suggested project setup for TypeScript development, please check out the [TypeScript Hello World app](https://github.com/SAP-samples/ui5-typescript-helloworld). It not only can serve as copy template, but also includes a [detailed step-by-step guide](https://github.com/SAP-samples/ui5-typescript-helloworld/blob/main/step-by-step.md) for creating this setup from scratch.
 
 The [TypeScript branch of the "UI5 CAP Event App"](https://github.com/SAP-samples/ui5-cap-event-app/tree/typescript) sample demonstrates a more complex application using the same setup. It comes with an [explanation](https://github.com/SAP-samples/ui5-cap-event-app/blob/typescript/docs/typescript.md) of what UI5 TypeScript code usually looks like and what to consider when writing such code.
 
-For quick and easy scaffolding of a new UI5 app written in TypeScript, you can also use the easy-ui5 tool with the [generator-ui5-ts-app](https://github.com/ui5-community/generator-ui5-ts-app) generator.
+For quick and easy scaffolding of a new UI5 app written in TypeScript, you can use the easy-ui5 tool with the [generator-ui5-ts-app](https://github.com/ui5-community/generator-ui5-ts-app) generator.
 
 ## Status
 
-The type definitions are in an experimental **_[Beta State](https://sap.github.io/ui5-typescript/beta-statement.html)_**. Changes are likely to occur,
-including potential **breaking changes**.
+We encourage you to use OpenUI5 with TypeScript productively for an improved development efficiency and experience. TypeScript itself keeps evolving and we try to further improve the UI5 type definitions, so there could be potential incompatible changes between versions of the type definitions. However, such incompatibilities would only affect the compilation of your code but will not cause runtime issues in your application. Plus, there are various ways to easily deal with them: you can, for example, simply keep using the previous version of the UI5 type definitions together with an updated UI5 runtime.
 
-For information on changes in the type definitions, in particular ones which require adaptation (but also new enhancements), please refer to the [Release Notes](https://sap.github.io/ui5-typescript/releasenotes.html).
+For news related to the type definitions, in particular ones which require adaptation, please refer to the [Release Notes](https://sap.github.io/ui5-typescript/releasenotes.html).
 
 ## License
-OpenUI5 and the type definitions are copyright by SAP and contributors and licensed under [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0).
+OpenUI5 and the type definitions in this package are copyright by SAP and contributors and licensed under the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openui5/types",
-  "version": "1.115.1",
+  "version": "1.116.0",
   "description": "OpenUI5 TypeScript Definitions",
   "homepage": "https://sap.github.io/ui5-typescript",
   "author": "SAP SE (https://www.sap.com)",

package/types/index.d.ts

@@ -16,9 +16,15 @@
 */
 
 /**
- * This is a Beta version of the OpenUI5 TypeScript signatures.
- * Significant changes may occur in future versions,
- * including potential breaking changes.
+ * We encourage you to use SAPUI5 with TypeScript productively for an
+ * improved development efficiency and experience. TypeScript itself keeps
+ * evolving and we try to further improve the UI5 type definitions, so there
+ * could be potential incompatible changes between versions of the type
+ * definitions. However, such incompatibilities would only affect the
+ * compilation of your code but will not cause runtime issues in your
+ * application. Plus, there are various ways to easily deal with them:
+ * you can, for example, simply keep using the previous version of the
+ * UI5 type definitions together with an updated UI5 runtime.
  */
 /// <reference path="./sap.ui.codeeditor.d.ts"/>
 /// <reference path="./sap.ui.commons.d.ts"/>