-
Notifications
You must be signed in to change notification settings - Fork 42
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
BUG - preview middleware uses fixed list of ui5 libs although the list is version dependent #2683
Comments
@heimwege Looking at this again I think we we can use from https://ui5.sap.com/resources/sap-ui-version.json http://localhost:8080/resources/sap-ui-version.json ( via npm run start-local ) |
@devinea I had a similar idea but then wasn't sure because currently the static list contains e.g. I recently included a function to fetch the ui5Version from sap-ui-version.json when refactoring the way we preview apps using UI5 2.x. So we just need to enhance that one to be able to either read the UI5 version or get the list of all libs or something. Shouldn't be a big deal 🤞🏻 |
I recently encountered an internal ui5 library matching the a namespace in the static list but not part of standard UI5 delivered libraries. So I think better to move away from namespaces to use the full lib names instead. |
Description
preview-middleware uses a list) of UI5 libs. That list seems to be UI5 version specific (compare 1.120.24 to latest). So it needs to be adjusted to a more dynamic list.
More Details see https://github.com/SAP/open-ux-tools/pull/2613/files#r1872645371
Steps to Reproduce
Steps to reproduce the behavior:
Expected results
Actual results
Screenshots
If applicable, add screenshots to help explain the problem.
Version/Components/Environment
Add any other context about the problem here
OS:
Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}
The text was updated successfully, but these errors were encountered: