coexisting-angular-microfrontends icon indicating copy to clipboard operation
coexisting-angular-microfrontends copied to clipboard

Routes with outlets inside of lazy module

Open diogolPereira opened this issue 4 years ago • 7 comments

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).

diogolPereira avatar Apr 28 '20 14:04 diogolPereira

someone have any news related to that issue

diogolPereira avatar May 11 '20 17:05 diogolPereira

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?

joeldenning avatar May 11 '20 18:05 joeldenning

Did you have some more information about that ? @arturovt @joeldenning

diogolPereira avatar Jun 04 '20 12:06 diogolPereira

someone have any news related to that issue @joeldenning

diogolPereira avatar Sep 09 '20 15:09 diogolPereira

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.

joeldenning avatar Sep 11 '20 21:09 joeldenning

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 avatar Sep 11 '20 21:09 joeldenning

@joeldenning thanks for feedback i will reopen the issue in single-spa-angular

diogolPereira avatar Sep 14 '20 10:09 diogolPereira