Reputation: 97038
ngOnChanges
is deprecated in favour of ngAfterChanges
, but the former was given a list of properties that changed. The latter gets nothing. How do I know what changed so I can only perform expensive actions if a particular @Input
changed?
Upvotes: 1
Views: 1378
Reputation: 1899
Calculating the list of changes was actually expensive itself. So it was dropped instead I would suggest having a setter mark if something has changed for just the expensive inputs.
Upvotes: 2