Problem Description
See #11666
Proposed Solution
The idea is to run the Vaadin UI and Angular UI in parallel. We will not embedded one UI into the other. Instead, we will use the different views of SORMAS as the separation between the two frontends. In other words, we will switch between both frontends using links.
E.g. .../sormas-ui/#!cases would be provided by the Sormas Vaadin UI, while .../sormas-web/about would be provided by the Sormas Angular UI.
Create a POC and based on that do the following:
- sormas-web module in the SORMAS-Project repository with all the basic dependencies that can be copied from SORMAS-Angular OR keep the angular app in the existing repository? The second option would only be a temporary solution. Long-term the whole vertical slice from backend to frontend should be in one repository.
- Navigation menu that looks like the one of the current Vaadin application and needs to be configured based on which features are available (as configured in the backend) and thus have an entry in the navigation menu.
- An easy way to provide URL of each view, so the correct frontend is used. This either needs to be kept in sync for both frontends or use a shared logic in the backend (preferred).
Furthmore:
Nice to have / future:
- Some views may be available in both UIs - for those it would be nice to allow the user to switch between both.
Additional Information
Ideally we would be able to use this so #11533 can be implemented in the new frontend.
Problem Description
See #11666
Proposed Solution
The idea is to run the Vaadin UI and Angular UI in parallel. We will not embedded one UI into the other. Instead, we will use the different views of SORMAS as the separation between the two frontends. In other words, we will switch between both frontends using links.
E.g.
.../sormas-ui/#!caseswould be provided by the Sormas Vaadin UI, while.../sormas-web/aboutwould be provided by the Sormas Angular UI.Create a POC and based on that do the following:
Furthmore:
Nice to have / future:
Additional Information
Ideally we would be able to use this so #11533 can be implemented in the new frontend.