Provide Automatic Binding of FormControl Error Messages and Status to input hints
- Lenguaje dominante
- TypeScript
- Estrellas
- 25k
- Forks
- 6.8k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 91
Descripción
#### Bug, feature request, or proposal:
This is a feature request.
This is related to #348, but is specifically asking for the material guidance to be a part of the framework, integrating with standard functionality of @angular/forms.
#### What is the expected behavior?
Looking at [Material Error Patterns](https://material.io/guidelines/patterns/errors.html), there seems to be a standard behavior of inlining form error message into the hint area (with a specific color).

It also supports separating the existing hint from the error message via a comma.

#### What is the current behavior?
Error state and messages are not handled.
#### What are the steps to reproduce?
There is nothing to show as this is feature that is yet to be implemented. [Material Error Patterns](https://material.io/guidelines/patterns/errors.html) should provide the expected behavior and visual treatment.
#### What is the use-case or motivation for changing an existing behavior?
The general gist is that if everyone were to follow the guidelines from material.io, you would end up with a fair amount of duplicate code for every input. The pervasiveness of the desired functionality seems like a prime candidate for handling at the framework level.
#### Which versions of Angular, Material, OS, browsers are affected?
All
#### Is there anything else we should know?
Guía de contribución
Línea de trabajo
Comienza con la referencia de Material Error Patterns y la integración de @angular/forms de Angular descrita en el issue. Como no se nombra ningún archivo ni prueba, identifica los puntos de entrada del framework y define la cobertura para la visualización automática de errores/estado, la separación de sugerencias y el tratamiento visual solicitado; se considera completado cuando el comportamiento se proporciona a nivel del framework en lugar de duplicarse por cada campo de entrada.
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
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100