Can you please maintain directory structure in __target__/ ?

未关闭
#855 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript, python
领域
compilers

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
2.9k
派生
218
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

TranscryptOrg/Transcrypt 的其他 Issue

查看 TranscryptOrg/Transcrypt 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。