fix: use ngOnChanges instead of effect to avoid signal-writes error

fix: use ngOnChanges instead of effect to avoid signal-writes error #3