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
While testing the ng-web-component-mixed branch, I found failures in the navigation between microfrontends, but the navigation from shell to microfrontend works correctly.
Initially to be able to navigate from the host to the microfrontends I had to share the remoteEntry to the WrapperComponent:
If the remoteEntry is not added, the following error is generated:
Well, with the remoteEntry added and trying to navigate between microfrontends, the URL changes but the component does not load, it seems that the navigation is trying to resolve to the origin microfrontend (I also made use of the connectRouter function that Mandred Steyer shares with us):
According to the analysis carried out, navigation from a microfrontend without web-component to the host or to another microfrontend with web-component works well, but navigation from a microfrontend with web-component to an external route (host or another microfrontend) does not work.
Has anyone been able to solve this problem with navigation to external routes using microfrontends with web-component? Thank you
The text was updated successfully, but these errors were encountered:
TCar10s
changed the title
Navigation between microfrontends does not work
Navigation between micro frontends with web-components does not work
Mar 13, 2024
While testing the
ng-web-component-mixed
branch, I found failures in the navigation between microfrontends, but the navigation from shell to microfrontend works correctly.Initially to be able to navigate from the host to the microfrontends I had to share the remoteEntry to the WrapperComponent:
If the remoteEntry is not added, the following error is generated:
Well, with the remoteEntry added and trying to navigate between microfrontends, the URL changes but the component does not load, it seems that the navigation is trying to resolve to the origin microfrontend (I also made use of the connectRouter function that Mandred Steyer shares with us):
According to the analysis carried out, navigation from a microfrontend without web-component to the host or to another microfrontend with web-component works well, but navigation from a microfrontend with web-component to an external route (host or another microfrontend) does not work.
Has anyone been able to solve this problem with navigation to external routes using microfrontends with web-component? Thank you
The text was updated successfully, but these errors were encountered: