coexisting-angular-microfrontends
coexisting-angular-microfrontends copied to clipboard
Routes with outlets inside of lazy module
I have a problem with routes with outlets inside a lazyloading module.
APP1Routing module:
const routes: Routes = [
{
path:'app1',
children:[
{path:'child',component:ChildComponent},
{path:'outlet',outlet:'example',component:OutletComponent},
{path:'lazy',
loadChildren:()=>import('./lazy/lazy.module').then(m => m.LazyModule)
},
]
},
{ path: '**', component: EmptyRouteComponent },
];
LazyModule routing:
const routes: Routes = [`
{
path:'',
component:LazyComponent,
children:[
{path:'child',component:ChildLazyComponent},
{path:'outlet',
outlet:'example',
component:OutletLazyComponent},
]
},
];
Console don't display errors or warnings.
Ps: I create one fork with the example (https://github.com/diogolPereira/coexisting-angular-microfrontends).
someone have any news related to that issue
I took a quick look at this and didn't make it very far. Angular isn't my strength. @arturovt do you have time to look at this?
Did you have some more information about that ? @arturovt @joeldenning
someone have any news related to that issue @joeldenning
I no longer spend much time helping maintain single-spa-angular, leaving it for others to maintain. There are a few people helping maintain it - I am not sure when they'll have time to look at this. The reason I've stopped putting a lot of time into maintaining it is that I don't know Angular well and single-spa-angular consumes more time than the combined time I spend on single-spa, single-spa-react, single-spa-vue, and all other single-spa libraries. The time I spent on single-spa-angular was often long and frustrating, so I've taken a step back.
One thing to note is that it might be best to reopen this issue on single-spa-angular instead of this example repo - the single-spa-angular repo is where we track angular-related issues.
@joeldenning thanks for feedback i will reopen the issue in single-spa-angular