Keep track of why files are in the program#40011
Conversation
…ut related file information is reattached to correct location
…and related information location changes
831475a to
300c727
Compare
|
@typescript-bot pack this |
|
Heya @sheetalkamat, I've started to run the tarball bundle task on this PR at 3a4613e. You can monitor the build here. |
|
@typescript-bot pack this |
|
Heya @sheetalkamat, I've started to run the tarball bundle task on this PR at 87ca884. You can monitor the build here. |
|
Hey @sheetalkamat, I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build. |
|
Trying on a local build just to see how it feels |
|
I like the idea, I would prefer different output. Maybe one line per file for easier regex/grepping? |
Files can have multiple reasons for being in the program - how do you think that should be handled as a single-line format? |
|
Huh, didn't catch that from the example 😅- I would say to repeat the file name on both lines. Would that be reasonable? |
|
Ready for review. |
|
I see that the |
|
|
I read that, but looking for the ways to access them. Is there is any new API for the same? |
|
It was always internal (meaning subject to change). We do not plan to expose that through API. |
|
Any easily parseable format would be nice JSON or directly graphviz style files; would allow for visualizations and tooling. |
--explainFilesis specified and program can use it too (earlier program wasnt aware of these)rootDiror doesn't match casing etcFixes #33515