Promote standalone component helpers to public API
- Lenguaje dominante
- TypeScript
- Estrellas
- 27k
- Forks
- 11.8k
- Merge medio
- 14 h 23 min
- PR fusionados (30 d)
- 162
Descripción
### Command
add
### Description
With https://github.com/angular/angular-cli/commit/e895fc7c1012796442cb7a4a3b9b3a0ec3845b0e a few standalone helpers were moved from the CDK to the schematics package. I am wondering why they were moved to a "private" section and aren't considered public API. Was this just because standalone components were still in developer preview at that time? Now that angular 15 is going to make standalone components stable could the helpers be moved outside the private section and be treated as public API?
### Describe the solution you'd like
With standalone components becoming stable these helpers should become public API as well.
### Describe alternatives you've considered
_No response_
Guía de contribución
Línea de trabajo
Comienza con el commit e895fc7c1012796442cb7a4a3b9b3a0ec3845b0e e inspecciona las funciones auxiliares independientes trasladadas del CDK al paquete schematics. Determina cómo la sección privada las expone y, después, verifica que las funciones auxiliares se traten como API pública y actualiza o añade la cobertura relevante si el paquete la tiene.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 38/100