SAP UI5 2.0 and deprecated APIs policies

[pubmikeb]

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?

[codeworrior]

Almost¹ 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

• 1.x: https://sdk.openui5.org/api/deprecated
• 2.x: https://sdk.openui5.org/nightly/2/#/api/deprecated

There won't be a ui5-legacy package for the deprecated stuff.

Footnotes

1. Why "almost": as can be seen in the 2.x link, there are some APIs documented as deprecated before 1.120, but they won't be removed. In fact, they are inherited from base classes, but not supported in the subclasses. The deprecation is just used as a mean to express that in a highly visible manner. We'll hopefully change the visualisation of those cases and no longer classify them as deprecated, rather as "inherited, not supported". ↩

[pubmikeb]

@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 1.120 (including), but totally, everything till the UI5 2.0 release. Migration to UI5 2.0 will anyway require the existing UI5-apps codebase modification, after all.

[flovogt]

@sbck70 @jnsttl