Frank Weigel

Ehm, if I'm not mistaken, `getSecurityToken` is an instance method. Did you mean `(new ODataModel()).getSecurityToken()`.

> BTW, I assumed, that UI5 Linter just parses usage of a module's methods and checks it against the list of deprecated APIs. Understandable, but we have methods like `v4.ODataModel#getProperty`...

Sorry, I have to correct myself. @matz3 reminded me that for `Controller#byId`, we already [merge knowledge from the XMLViews](https://github.com/SAP/ui5-linter/blob/main/src/linter/xmlTemplate/ControllerByIdInfo.tshttps://github.com/SAP/ui5-linter/blob/main/src/linter/xmlTemplate/ControllerByIdInfo.ts) into the signature of the controller's `byId` call. Just for `getModel`...

Almost[^1] everything deprecated up to 1.120 (including) will be removed. https://github.com/SAP/openui5/tree/main can give you an impression of that. It's not the final state, but shows the direction... You might also...

Some comments: > Apart from the above documented restrictions; when assigning enum values declaratively in XML or manifest.json, the actual enum values visible in the source code must be passed...

This is caused by a mismatch of your manifest version wrt. the UI5 version. The UI5 tooling 4.0 enhances the manifest, json with information about the `supportedLocales`. But in UI5...

You can find the mapping between manifest versions and UI5 versions [here](https://sdk.openui5.org/#/topic/be0cf40f61184b358b5faedaec98b2da)

I just said to @randombyte that I would expect this as the next question :-) Sure, a warning would be nice. For some historic reasons, the runtime does not check...

BTW: thank's for the fast and easy to reproduce feedback reg. tooling 4.0 :-)

BTW: Something into the direction of this enhancement request has been implemented with 429f584d86e83e20ea67aa0940e079e0d780d3ba . The methods of [sap/base/Log.js](https://openui5nightly.hana.ondemand.com/#/api/module%3Asap%2Fbase%2FLog) now allow to specify an error object as `sDetails` parameter (2nd...