When upgrading to Angular 4, I am getting the following warning in the console:
it looks like you're using the disabled attribute with a reactive form directive. If you set disabled to true when you set up this control in your component class, the disabled attribute will actually be set in the DOM for you. We recommend using this approach to avoid 'changed after checked' errors.ֿ
When doing something like this:
<input type="text" formControlName="name" [disabled]="isDisabled">
it's seems that Angular does not like anymore when we use the disabled property on form control.
What is changed and why it's happening?
form-groupsandcontrolsin the component code. if not it will show that warning - Aravind