Skip to content
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

Open
pubmikeb opened this issue Oct 14, 2024 · 4 comments
Open

SAPUI5 2.0 and deprecated APIs policies #4145

pubmikeb opened this issue Oct 14, 2024 · 4 comments
Assignees

Comments

@pubmikeb
Copy link

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
Copy link
Member

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

  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
Copy link
Author

pubmikeb commented Oct 14, 2024

@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
Copy link
Member

flovogt commented Oct 15, 2024

@sbck70 @jnsttl

@marianfoo
Copy link
Contributor

@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:
https://marianfoo.github.io/ui5-lib-diff/?versionFrom=1.120.0&ui5Type=OpenUI5&versionTo=1.108.25

@flovogt flovogt changed the title SAP UI5 2.0 and deprecated APIs policies SAPUI5 2.0 and deprecated APIs policies Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants