microsoft / microsoft/TypeScript
Review the project setup experience
Abierto
@DanielRosenwasser ya está trabajando en esto.
Desde el 18/11/2020.
Needs Proposal
Rescheduled
Suggestion
- Lenguaje dominante
- Go
- Estrellas
- 111k
- Forks
- 14.3k
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 132
Descripción
Today, tsc --init creates a big-ol' file that is super intimidating. We try to provide comments and blocks of sections to give people a clear separation of config concerns. We also provide a link to https://aka.ms/tsconfig.json.
We also have a belief that most people don't even use tsc --init.
That said, there are problems, and tsc --init doesn't make it totally clear what the "best practices" are for starting a project. Things that are missing:
- Project layout guidance (e.g.
src,tsconfignaming) - "well known"/"blessed" flags as opposed to just ONE BIG PAGE of ALL THE FLAGS 😨
- Easy way to find the information regardless of whether a user used
tsc --init
In short:
- Docs for tsconfig.json "getting started"
- Link to that in generated tsconfig.json
- Re-evaluate generated tsconfig content.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.