Robert Ernens

@udos86 Hi Udo > When using this change detection you actually need to create new instance of your form (control) model to trigger a component update I am not sure...

@udos86 Still having the pb but have circumvented it using standard formcontrol access not through the model

@Karamuto I am not as good as you are at this. I have made a pull request with a very simple implementation that address backward compatibility as well as the...

@Karamuto Yes, you are right. My PR leaves the current behavior untouched while allowing to implement material with object in autocomplete list.

@monstrfolk use the following method ``` public dataToForm( data: any, formModel: DynamicFormModel ) { Object.keys(data).forEach( key => { const model = this.formService.findById( key, formModel ) as DynamicInputModel; if ( model...

@monstrfolk patchValue is a formGroup method not a formModel method, I strongly recommend to use the formModel methods when using ng-dynamic-forms. I do that in hundreds of forms with data...

@monstrfolk assume your data structure is the following and matches the way your form is built: ``` { name: 'my name', birthDate: 'any date', address: { name: 'my address name',...

@udos86 Hi Udo, what kind of technical insight would you like ?

@udos86 it is stated in the Angular documentation and I remember having read that in an article that was exploring Angular 6 in depth. Will do some research in my...

@udos86 hi Udo, looking into this for a project currently going on, I have faced two issues : 1. if the attached list is an observable, mat-autocomplete does not work...