Andreas Kunz

See https://github.com/SAP/openui5/commit/ea0b15cda111284864c863bbad9b20225bea6134

@Revest117 This was an obvious improvement idea from the very beginning and there is actually already [code that identifies the changed files](https://github.com/SAP/ui5-typescript/blob/main/packages/ts-interface-generator/src/typeScriptEnvironment.ts#L154) (did I mention I hate the prettifier-enforced formatting?)....

Actually, https://github.com/SAP/ui5-typescript/blob/main/packages/ts-interface-generator/DEVELOPMENT.md#in-practice has some thoughts on this as well and some change detection details.

Sorry for the delay (vacation time...). Our focus is on the "ts-types-esm" flavor of the type definitions right now, not the "ts-types" definitions which still define all the globals ("sap.m.Button"...

To avoid the impression nothing is happening here: getting rid of synchronous XHRs is not an atomic task. Every single usage has other effects on existing applications and public APIs...

Hi @RobertoMalatesta , by now, no parts of at least OpenUI5 should trigger sync requests on their own anymore. Plus, for all sync APIs in OpenUI5 (which we cannot simply...

@iljapostnovs If I don't miss anything, there is even already a pull request for this: https://github.com/SAP/ui5-typescript/pull/357 However, that one is stuck a bit, as such generic classes cannot be used...

Actually, this is the same issue that I more generically reported as https://github.com/SAP/ui5-typescript/issues/327: permutations are missing for a few UI5 API objects, which are no proper classes, interfaces or namespaces....

Issue is understood and fixed in the internal generator repo. Which type definitions version has the fix depends on when the fixed version is used in the internal build.

Hi Timo, thanks a lot for your detailed feedback! We're definitely looking into it. Promisification of the V2 ODataModel has been rejected recently (https://github.com/SAP/openui5/issues/3058), but I think it doesn't hurt...