-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
ngOnChanges called twice #88
Comments
Hi @jerousseau, Sorry for late response. Just got my hands on your plunkr. I can confirm that this is a bug. Thanks for building awesome example. |
…hanged So that OnChanges hook is called only once closes #88
🎉 This issue has been resolved in version 2.1.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I am still experiencing this issue, perhaps only a change detection issue but not sure, using version 3.0.0 |
@Alandroid can you please create a plunkr with repro? |
Hi,
When we change the component on the fly, the ngOnChanges of the new component is called twice, first time with the inputs we have passed to the new component ( firstChange: true and no previousValue) and a second time with in previousValue the value of the old component.
Any idea to avoid this ?
Thanks
Plnkr example to reproduce : https://plnkr.co/edit/uM7FzOmI4wNPE4F8WtFR
The text was updated successfully, but these errors were encountered: