Andreas Kunz

Hm. The situation is like this: - v2.ODataModel code returns undefined or null (or a context, of course; and claims it returns context or undefined) - v4.ODataModel returns always a...

> If you say TypeScript really requires it we may enhance the return value documented for Model#createBindingContex Isn't correctness also a good reason to change documentation?

Hi Pieter, I'm not exactly sure how you got there. In the "js-with-typescript-support" branch you specified we have plain traditional UI5 JavaScript without ECMAScript modules. I'm not sure why you...

@pubmikeb Sorry for not responding. Well, yes, my code snippet was misleading. Importing `sap/ui/core/library` but claiming the `@param` is `import("sap/ui/core/library").IAsyncContentCreation` and using it as such will satisfy TS, but of...

@Revest117 thanks for your preparation work. Despite the lack of reaction here, we haven't ignored this topic, but the implementation is tricky: you know, the type definitions of UI5 are...

FYI: we have enriched the JSDoc processing to enable specifying inheritance in `@typedef`. So we are going to express the above types directly in the UI5 source code and have...

Thanks for reporting! It's because Core is not an EventProvider - only for them the APIs are generated automatically. In the Core, these methods (attach... detach... etc. are explicitly written,...

Does ```ts action: keyof typeof MessageBox.Action ``` in the second line work for you to have at least *some* simplification? I think it should, as the keys (alternative proposal) equal...

@dfenerski > `JQuery.Event` is not generic True, but it's defined by jQuery, not by us. We could probably extend it, but yeah, not really investing into jQuery anymore. Plus, I...

@gssales It was done because this fits the UI5 runtime. Previously, dynamic imports like `import("sap/m/MessageBox").Action` seemed to work in TypeScript, but did *not* work with the actual UI5 runtime after...