-
Notifications
You must be signed in to change notification settings - Fork 93
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
Router events triggered unexpectedly when a component is rendered #318
Comments
This is an intended behavior to reflect a "running" application. I would suspect the running app to behave the same way though, maybe it isn't because event would already be processed? I'll have to investigate this, perhaps it would be better to invoke the |
Thanks for reply. I have tested it in a running app but didn't see this behaviour. This is the repo: https://github.com/ruoxin-mx51/ng14-apple-banana |
Thanks @ruoxin-mx51, this will get fixed soon. |
🎉 This issue has been resolved in version 13.0.0-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 13.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The router events will be trigger when a component is rendered.
Given a component
and its test
Now run the test then you can see the router events (which won't show up with Angular TestBed or when running the app)
Is this an intentional behaviour? (FYI I believe this behaviour was introduced in version 11.0.3: #286)
The text was updated successfully, but these errors were encountered: