-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SAPUI5 2.0 and deprecated APIs policies #4145
Comments
Almost1 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 compare There won't be a ui5-legacy package for the deprecated stuff. Footnotes
|
@codeworrior, thanks for the extremely prompt response! Actually, less legacy we have — better it is, so it would be great to delete all legacy not only till |
@pubmikeb you can look also at this list if you want to know what is deprecated, 2.X is not yet integrated. You can compare two different versions to have a complete list of deprecated APIs: |
The SAP UI5 2.0 release is hopefully approaching and thus, I have a question.
For the last couple of years, the UI5 code base has undergone significant changes with a massive APIs deprecation. As a result, currently, there are a lot of deprecated APIs (modules, classes, methods, etc.), which are still available for consumption due to backward compatibility reasons.
Are there already any plans for what will be done with deprecated APIs in the coming SAP UI5 2.0? Will these components be extracted to the
ui5-legacy
-package (for backward compatibility reasons, if required) and delivered separately to ensure the optimum experience for the legacy-free apps by reducing the codebase size of UI5 2.0 and boosting the loading time for the apps, which do not use the legacy APIs? Or will the deprecated APIs remain a part of the general UI5 2.0, polluting the heavily refactored codebase?The text was updated successfully, but these errors were encountered: