Typescript Status
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- typescript
- Área
- documentation
Línea de trabajo
Empieza leyendo este issue de estado y el proyecto react-docgen-typescript referenciado. El payload no menciona ningún archivo del repositorio, prueba ni punto de entrada, y no define ningún cambio ni criterio de finalización, por lo que aquí no hay un camino de implementación concreto que seguir.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
The overall development speed, as well as the frequency of new features and releases, has slowed down over the past few years. This is partly because I now have less time to dedicate to open source work. But more importantly, I believe the project has reached a critical turning point. Let me explain.
When this project started—before TypeScript was widely used—statically analyzing code to extract PropTypes was a reasonable solution. Most people used PropTypes in a fairly straightforward way, which made it easy for react-docgen to detect and interpret them. Even more complex use cases were manageable, because the underlying idea of PropTypes was relatively simple.
Fast forward to today: TypeScript has become the dominant way to type React props. react-docgen has some decent support for TypeScript—at least for the more common use cases. But TypeScript is a constantly evolving system, and it can be used in very sophisticated ways. This makes it increasingly difficult to cover all scenarios using static analysis alone.
While working on some of the more recent PRs, I realized that much of my time was spent effectively reimplementing how TypeScript works—trying to understand and reproduce its behavior just to infer component prop types. At that point, it started to feel like the project was heading in the wrong direction. I simply can’t keep up with the scale of what the TypeScript team and its much larger community are building.
There’s a project called react-docgen-typescript which I believe follows a more sustainable approach for TypeScript support. There may be even better options out there, but I don't currently have the time to invest in a shift of this magnitude.
So if you need better TypeScript support, I recommend giving react-docgen-typescript a try.
- Lenguaje dominante
- TypeScript
- Estrellas
- 3.8k
- Forks
- 316
- Merge medio
- 2 h 29 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la 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.
Más de reactjs/react-docgen
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
reactjs/react-docgen#1102 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
reactjs/react-docgen#997 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 42/100
reactjs/react-docgen#994 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
reactjs/react-docgen#982 · 2 comentarios ·
-
Escapable commas in CLI options?Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
reactjs/react-docgen#962 · 1 comentario ·
Todos los issues de reactjs/react-docgen
Issues similares
-
bug HemiStake
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
hemilabs/ui-monorepo#2413 ·
Los mantenedores suelen responder en 1 día
-
component/ui framework/react kind/bug language/javascript
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
meshery/meshery#22216 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
company delete fails with 500 on any company that has activity (cost events, inbox dismissals)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
paperclipai/paperclip#14982 ·
Los mantenedores suelen responder en 1 día
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
lingdojo/kana-dojo#31515 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día