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

[micro-frontend]: --sap* variables conflicts #7696

Closed
nnaydenow opened this issue Oct 11, 2023 · 0 comments · Fixed by #7703
Closed

[micro-frontend]: --sap* variables conflicts #7696

nnaydenow opened this issue Oct 11, 2023 · 0 comments · Fixed by #7703
Assignees
Labels
enhancement New feature or request TOPIC Core

Comments

@nnaydenow
Copy link
Contributor

nnaydenow commented Oct 11, 2023

Background

If ui5-webcomponents are used in micro-frontend scenario --sap* variables conflicts. Currently the used variables are defined by the latest registered runtime by the time of the registration, not by version which leads to broken components in following scenario: We have 1 main application and 1 widget where both are using ui5-webcomponents. Main application is the first registered runtime and it's using version 1.18.0. The widget is the second registered runtime and it's using version 1.15.0.

Expected Behaviour

--sap* variables from version 1.18.0 to be used.

Description

Investigate possible solution of how we can decide which variables to be loaded.

@nnaydenow nnaydenow added bug This issue is a bug in the code enhancement New feature or request TOPIC Core and removed bug This issue is a bug in the code labels Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request TOPIC Core
Projects
Status: Completed
Development

Successfully merging a pull request may close this issue.

2 participants