Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notifications not showing #242

Open
vytautas-pranskunas- opened this issue Sep 1, 2022 · 2 comments
Open

Notifications not showing #242

vytautas-pranskunas- opened this issue Sep 1, 2022 · 2 comments
Labels
needs repro Indicates that this issue needs a reproduction before further steps can be taken type: bug Indicates an unintended behaviour, unexpected problem, crash

Comments

@vytautas-pranskunas-
Copy link

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.

@dominique-mueller dominique-mueller added type: bug Indicates an unintended behaviour, unexpected problem, crash needs repro Indicates that this issue needs a reproduction before further steps can be taken labels Sep 13, 2022
@vytautas-pranskunas-
Copy link
Author

Hello,

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

@vytautas-pranskunas-
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs repro Indicates that this issue needs a reproduction before further steps can be taken type: bug Indicates an unintended behaviour, unexpected problem, crash
Projects
None yet
Development

No branches or pull requests

2 participants