-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Is it possible to support old version of UI5 #310
Comments
Interested in the same question! |
Hi, for identifying the UI5 Controls we use the Record Replay API which is only available since 1.60. Below that, there should be an error in the terminal that the UI5 version is too low. I also had a quick look in the documentation and it seems like we are missing this prerequisite. Thanks for pointing that out! Unfortunately I can not give you an answer to the rest of your questions. Maybe @vobu or someone else can help you here. |
for UI5 < 1.60, we'd have to come up with a different client-side mechanism for retrieving a UI5 control and proxying it from browser- to Node-scope. Certainly doable, but quite an effort. As the separation of concern is clear here ("support UI5 < 1.60"), I see this very well suited for an external contribution. Anyone jumping to the occasion? 😄 |
started an exemplary (albeit statistically probably invalid 😝) poll: https://twitter.com/_wdi5_/status/1552199429364617217?s=21&t=3CAvEgHO0ZGjivVzMI5o-Q |
Could we bring the missing code from a higher version of UI5 to version 1.38, what would it means from a licensing point of view ? Should we ask UI5 to add it ? |
Some projects are running version
1.38
of UI5 which will be supported for a long time (up to 2027 according to version overview.However, it seems that it does not work with WDI5 (probably because of the missing OPA helpers).
Is there a strategy to handle old versions of UI5 ?
If not, is the minimum version documented ?
What are the alternatives ?
The text was updated successfully, but these errors were encountered: