Closed joeldenning closed 4 years ago
Hi,
Any update on this?
Hi @jaspreet1234567, I am working on https://github.com/CanopyTax/single-spa-angular/issues/44 and https://github.com/CanopyTax/single-spa-angular/issues/41 first before shifting attention to this bug.
oops accidentally closed. Reopening now
I am getting the similar issue when same name module existing in two different apps with lazylaod (with BrowserAnimationsModule)
Try to navigate from app1 to app2 having the same module with lazyloading.
When I have two different apps both where lazy loaded and using BrowserAnimationsModule and while navigating between each other have same module names errors the above errors for me as well.
Same error here.
When I navigate to a nested route and came back to a previous page, the change detection doesn't work, I have to manually put a detectChanges().
I'm using also Angular material and BrowserAnimationsModule and when I came back from another route I'm not able to use, for example, the datepicker. Things appear after a click event, but never automatically.
@jaspreet1234567 I cloned your repo and the issue really presents there. But the issue disappeared when I upgraded single-spa-angular
to 3.0.0
.
@HemTech @SunilManthenaG01 @danyjaen gentlemen, your issues are impossible to test and resolve unless you provide minimal reproducible examples.
Thanks @arturovt - I'm closing this issue as fixed in single-spa-angular@3. If that turns out not to be true, please provide a minimal reproducible example.
This issue was first reported as a comment to a separate issue. https://github.com/CanopyTax/single-spa/issues/289#issuecomment-483105297
It is from @jaspreet1234567