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
needs reproIndicates that this issue needs a reproduction before further steps can be takentype: bugIndicates an unintended behaviour, unexpected problem, crash
i have complex project with OnPush change detections and lazy loaded routes.
If i keep notification-container in app.component.html - notifications does not show when triggered from different services
If i put notification-container to first neseted route - Layout - notifications starting to come up.
I would like to keep it in app.component.html because i can have multiple layouts and would not like to init notificationModule in each of those.
The text was updated successfully, but these errors were encountered:
i still strugling to get i working... notifications just do not show.. my best guess that it is becaus eog lazy loaded modules. Because usually with lazy loaded models libraries has .forChild() ...
p.s. i have made a workaround for now - have intorduced my own service which emits notification. In app.component there is a subscription that listens for those emits and triggers notifier :( ugly but working
needs reproIndicates that this issue needs a reproduction before further steps can be takentype: bugIndicates an unintended behaviour, unexpected problem, crash
Hello,
i have complex project with OnPush change detections and lazy loaded routes.
If i keep notification-container in app.component.html - notifications does not show when triggered from different services
If i put notification-container to first neseted route - Layout - notifications starting to come up.
I would like to keep it in app.component.html because i can have multiple layouts and would not like to init notificationModule in each of those.
The text was updated successfully, but these errors were encountered: