1. ngOnChanges is called before ngOnInit but after constructor()
2. ngOnChanges is called because of @Input() obj, obj's reference changes. If you mutate one the object's prop, it won't trigger ngOnChanges, you have to create new object.
1. ngOnChanges is called before ngOnInit but after constructor()
2. ngOnChanges is called because of @Input() obj, obj's reference changes. If you mutate one the object's prop, it won't trigger ngOnChanges, you have to create new object.