Can you please maintain directory structure in __target__/ ?

Open
#855 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, python
Domain
compilers

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
2.9k
Forks
218
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TranscryptOrg/Transcrypt

All issues in TranscryptOrg/Transcrypt

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.