4 ms·
I've just tried this, and the most touched files are also the most irrelevant or boring files (auto generated, entry-point of the service etc.) in my tests.
by dewey 7mo ago
I've just tried this, and the most touched files are also the most irrelevant or boring files (auto generated, entry-point of the service etc.) in my tests.
- nulltrace 7mo agoYeah same thing happens with lockfiles and CI configs. You end up filtering out half the list before it tells you anything useful.
- deleted 7mo ago[deleted]
- pydry 7mo agoI just tried it too and it basically just flagged a handful of 1500+ line files which probably ought to be broken up eventually but arent causing any serious problems.
- Cthulhu_ 7mo agoIf it's (like in my case) dependency management, localization or config files, breaking them up will likely only cause more issues. Make sure that it's an actual improvement before breaking things up.
- mememememememo 6mo agoI'd only look at human/AI edited files (i.e. that require some kind of reasoning) not generated ones (where the reasoning is in the generator). Generation is precompilation. Entry point is interesting. Lots of scope to become a scary file.