MatRadioButton: Error: No value accessor for form control with path...
- Lenguaje dominante
- TypeScript
- Estrellas
- 25k
- Forks
- 6.8k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 91
Descripción
#### What is the expected behavior?
I'm trying to use the `mat-radio-button` inside an HTML table (agreed, the form is a bit stange). It's an array of data, for each row I need 2 radio buttons. I'm constructing the `FormArray` dynamically and then bind it into the HTML.
Note: Being in a table, where each of the grouped radio buttons is inside it's own ``, I cannot use `` but that shouldn't be an issue as I'm using the `name` attribute as you would with native controls.
#### What is the current behavior?
Right now the behavior is that I'm getting an error saying `No value accessor for form control with path: 'phoneNumbers -> 0 -> phone1'` etc...and hence the databinding doesn't work.
On the other side, if I change nothing else, but the `mat-radio-button` with native HTML radio buttons, everything works as expected (see repro stackblitz below).
#### What are the steps to reproduce?
Providing a StackBlitz reproduction is the *best* way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
Example using HTML native radio buttons: https://stackblitz.com/edit/angular-reactiveforms-dynamic-formarray-binding?file=app/person-edit.component.ts
(Failing) example using `mat-radio-button`: https://stackblitz.com/edit/angular-4k8hf4-3egfsd?file=app%2Fradio-overview-example.html
#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
latest from the current docs (i.e. `v7.2`)
Guía de contribución
Línea de trabajo
Empieza ejecutando el ejemplo de StackBlitz que falla en app/radio-overview-example.html y compáralo con el ejemplo native-radio en app/person-edit.component.ts. Reproduce el error informado para el FormArray dinámico y sigue la ruta del control de formulario. Está terminado cuando los controles mat-radio-button se enlazan correctamente en la tabla sin el error de value-accessor.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- frontend
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100