You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The angular app currently comes with a top menu, while the Vaadin "legacy" app uses a side menu.
To allow for a seamless switch between both apps, the angular app should come with a side menu that looks the same as the menu of the Vaadin app.
Proposed Change
Replace the top menu with a side menu that looks like the vaadin app's menu
Should be easy to adjust in code wheter a menu entry links to the angular app or the vaadin legacy app
When connected to a legacy app, all menu entries that are not angular exclusive, link to the legacy app
It's still possible to "manually" open any angular app view, using the URL
Implementation Details
Add a new side menu component that is used by default. The old menu should stay available in the code, but not be used for now.
Style the menu to look like the Vaadin menu, including the SORMAS logo
Add all menu entries in the same order as in the Vaadin app
Define vaadin UI "legacy" paths for all menu entries
Add an environment config that defines the host address of the vaadin app. If defined, all menu entries that have a legacy path should link to the legacy app instead of the angular app
markusmann-vg
changed the title
Introduce vaadin-style side menu and legacy links to the angular app
Introduce vaadin-style side menu and legacy links to the angular app [~8-13]
Apr 27, 2023
Problem Description
The angular app currently comes with a top menu, while the Vaadin "legacy" app uses a side menu.
To allow for a seamless switch between both apps, the angular app should come with a side menu that looks the same as the menu of the Vaadin app.
Proposed Change
Added Value/Benefit
See #11666
Acceptance Criteria
Implementation Details
Mockups
No response
Additional Information
https://github.com/hzi-braunschweig/SORMAS-Project/blob/development/docs/SERVER_SETUP.md#keycloak-as-a-docker-container and
https://github.com/hzi-braunschweig/SORMAS-Angular/blob/development/docs/auth-keycloak.md
Out of scope
The text was updated successfully, but these errors were encountered: