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
Is your feature request related to a problem? Please describe.
If you want to develop a application for cross main version support, you need to use deprecated APIs.
For example in this code sample to use MessageManager from Version 1.71 to 2.0 i still need to use the sap.ui.getCore():
try{// sap.ui.core.Messaging is only available in UI5 version 1.118 and above, prefer this over sap.ui.getCore().getMessageManager()saging = Util.loadUI5RessourceAsync("sap/ui/core/Messaging");constMessaging=awaitUtil.loadUI5RessourceAsync("sap/ui/core/Messaging");Messaging.removeAllMessages();return;}catch(error){Log.debug("sap/ui/core/Messaging not found",undefined,"SpreadsheetUpload: checkForODataErrors");}// fallback for UI5 versions below 1.118sap.ui.getCore().getMessageManager().removeAllMessages();
Describe the solution you'd like
When i would use the ui5 linter, this would be a error everytime the file is checked. So ignore file like in #170 does not help.
I would like to use something like a annotation similar to for example @ts-ignore
In this case i can run CI/CD pipelines explicity stating that this can be ignored.
Describe alternatives you've considered
Currently i don´t know how to workaround this.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
If you want to develop a application for cross main version support, you need to use deprecated APIs.
For example in this code sample to use
MessageManager
from Version 1.71 to 2.0 i still need to use thesap.ui.getCore()
:Describe the solution you'd like
When i would use the ui5 linter, this would be a error everytime the file is checked. So ignore file like in #170 does not help.
I would like to use something like a annotation similar to for example
@ts-ignore
In this case i can run CI/CD pipelines explicity stating that this can be ignored.
Describe alternatives you've considered
Currently i don´t know how to workaround this.
The text was updated successfully, but these errors were encountered: