Can you please maintain directory structure in __target__/ ?

Abierto
#855 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
javascript, python
Área
compilers

Línea de trabajo

The issue does not name files, tests, or entry points. Start by locating the Transcrypt compiler logic that writes generated files under target/ and compare its output paths with the source directory tree. Done means generated files preserve the original directory structure and the behavior works for projects with nested source directories.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

IS: exploratory

I am happy to use Transcrypt. It seems that the early developers were using Transcrypt for a small project with small number of source files. So, they had no problem with flat structure in target/ directory.

But, I am developing a pretty big project with many source files in complicated directory structure. So, during debugging time, choosing the source files from target/ directory is pretty stressful job . Moreover, I have to choose the source files again whenever I rerun. Web browsers reload all source files whenever reload most times (maybe when the source files are modified). I have to read and scroll from the top of a very long list of source files to choose to open every time I rerun. It takes a pretty amount of time when the number of source files is large.

I think that if target/ directory maintains the original source directory , this task choosing source files for debugging get easier. I hope that it is not complicated to change.

Thanks.

Lenguaje dominante
Python
Estrellas
2.9k
Forks
218
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TranscryptOrg/Transcrypt

Todos los issues de TranscryptOrg/Transcrypt

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.