bug(material/chip): Mdc Chip Grid empties all options when using Reactive Forms and focusing out
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
### Is this a regression?
- [X] Yes, this behavior used to work in the previous version
### The previous version in which this bug was not present was
14.2.6
### Description
Having Reactive forms attached to `mat-chip-grid` which accepts an array of object values, clears them on focus out.
### Reproduction
Steps to reproduce:
1. Create a formgroup with some formControl
2. Bind it to ` `
3. Add some new options (or the same works if the list is already populated) that are **arrays of objects**.
4. Focus out of the component
https://stackblitz.com/edit/angular-6g9jz1?file=src%2Fapp%2Fchips-input-example.ts,src%2Fapp%2Fchips-input-example.html
Upon further investigation, figured that the core problem is that on focus out, object values are transformed to strings hence why we don't see the name property. Nevertheless objects were not transformed in v 14.

_Note:_ In the Docs Chip list works as expected because it is not bound to Reactive forms
### Expected Behavior
All options remain with previously defined object values
### Actual Behavior
All options are transformed to strings thus we have empty text options
### Environment
- Angular: 15.0.4
- CDK/Material: 15.0.3
- Browser(s): Chrome 108.0.5359.124
- Operating System: macOS Ventura 13.1
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par la reproduction StackBlitz liée, en particulier src/app/chips-input-example.ts et src/app/chips-input-example.html, et examinez comment mat-chip-grid est lié à Reactive Forms avec des tableaux d’objets. Reproduisez le comportement lors de la perte de focus, puis vérifiez que les options conservent leurs valeurs d’objet et leur texte visible ensuite.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- frontend
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 42/100