This thign is frustrating to say the least about coreui-free-angular-admin-template HOT 1 CLOSED

Dear @Porkechebure

Thanks for your question. However, we kindly request that you refrain from using offensive language here. It will not help in any way.

You mentioned that the normal Angular way doesn’t work. It's possible that your issue may be related to a lack of familiarity with Angular and how it interacts with HTML attributes like disabled. See: https://angular.io/guide/binding-syntax#property-and-attribute-comparison

Additionally, you mentioned being unsure about why 'formGroup / controlsConfig' is defined in this manner. If you take some time to explore the Angular documentation, particularly the section on Reactive Forms, how operate FormGroup, FormControl with FormControlState, you may find the answers you're looking for and overcome the challenges and frustration you're facing.

Anyway, look at your 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.

Example:

  // Specify the `disabled` property at control creation time:
  form = new FormGroup({
    first: new FormControl({value: 'Nancy', disabled: true}, Validators.required),
    last: new FormControl('Drew', Validators.required)
  });

  // Controls can also be enabled/disabled after creation:
  form.get('first')?.enable();
  form.get('last')?.disable();

from coreui-free-angular-admin-template.