You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happens instead?
Console error: [DEPRECATED] The type 'sap.ui.core.TooltipBase' was accessed via globals. Defining types via globals is deprecated. In case the referenced type is an enum: require the module 'sap/ui/base/DataType' and call the static 'DataType.registerEnum' API. In case the referenced type is non-primitive, please note that only primitive types (and those derived from them) are supported for ManagedObject properties.
General annotaion: I'm wondering why deprecation warnings are presented as errors. This introduced a lot more efford than we expected on our side on a bugfix LTS update (1.120.0 to 1.120.12). We went through our whole codebase and fixed all type declerations in our source code, which is not what i expect from a bugfix release. IMHO these should have been presented as warnings to fix until the next major or minor release.
The text was updated successfully, but these errors were encountered:
Hello @pixel-fabian,
Thank you for addressing the issue in the control code. I've created an internal incident DINC0149840. The status of the issue will be updated here in GitHub.
OpenUI5 version:
1.120.12
Browser/version (+device/version):
Chrome
Any other tested browsers/devices(OK/FAIL):
Firefox (FAIL)
URL (minimal example if possible):
https://openui5.hana.ondemand.com/entity/sap.m.FeedInput/sample/sap.m.sample.FeedInput
Steps to reproduce the problem:
What is the expected result?
No console error
What happens instead?
Console error:
[DEPRECATED] The type 'sap.ui.core.TooltipBase' was accessed via globals. Defining types via globals is deprecated. In case the referenced type is an enum: require the module 'sap/ui/base/DataType' and call the static 'DataType.registerEnum' API. In case the referenced type is non-primitive, please note that only primitive types (and those derived from them) are supported for ManagedObject properties.
General annotaion: I'm wondering why deprecation warnings are presented as errors. This introduced a lot more efford than we expected on our side on a bugfix LTS update (1.120.0 to 1.120.12). We went through our whole codebase and fixed all type declerations in our source code, which is not what i expect from a bugfix release. IMHO these should have been presented as warnings to fix until the next major or minor release.
The text was updated successfully, but these errors were encountered: