Allow to open views contributed by the host app #271
Comments
danielwiehl
added a commit
that referenced
this issue
May 21, 2024
- provide view from host app - move view to interact with microfrontend platform to host app - remove test capability mechanism - consider removing workbench-client handles from host (dialog, message box, popup) - consider ignoring size set for a message box if provided by the host app - use actual test app names in register capability and register intention #271, #551
danielwiehl
added a commit
that referenced
this issue
May 21, 2024
- provide view from host app - move view to interact with microfrontend platform to host app - remove test capability mechanism - consider removing workbench-client handles from host (dialog, message box, popup) - consider ignoring size set for a message box if provided by the host app - use actual test app names in register capability and register intention #271, #551
danielwiehl
added a commit
that referenced
this issue
May 22, 2024
- provide view from host app - move view to interact with microfrontend platform to host app - remove test capability mechanism - consider removing workbench-client handles from host (dialog, message box, popup) - consider ignoring size set for a message box if provided by the host app - use actual test app names in register capability and register intention #271, #551
danielwiehl
added a commit
that referenced
this issue
May 22, 2024
- provide view from host app - move view to interact with microfrontend platform to host app - remove test capability mechanism - consider removing workbench-client handles from host (dialog, message box, popup) - consider ignoring size set for a message box if provided by the host app - use actual test app names in register capability and register intention #271, #551
danielwiehl
added a commit
that referenced
this issue
May 22, 2024
- provide view from host app - move view to interact with microfrontend platform to host app - remove test capability mechanism - consider removing workbench-client handles from host (dialog, message box, popup) - consider ignoring size set for a message box if provided by the host app - use actual test app names in register capability and register intention #271, #551
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
By using the
WorkbenchRouter, a micro app can open a view microfrontend from any other micro app except the host app. This should be changed so that the host app can also provide views that other micro apps can open using the same mechanism.Describe the solution you'd like
As with view microfrontends provided by client apps, it should be possible to register a view capability in the host app and specify the routed component with a path. Other micro apps should then be able to open that view using the
WorkbenchRouterby passing the respective qualifier. The microfrontend should not be embedded via iframe, but directly via Angular router.Note that the host can already provide popups as popup capabilities.
The text was updated successfully, but these errors were encountered: