nevinera
commented
8 months ago @danmayer - I came here to make this exact request. Right now the only way to tell if something becomes unused is to reset the data and wait. But there are plenty of infrequently used features, so you often need to wait a month or so before you can be confident that any given bit of code is actually dead and removable. That makes the debriding cycle time very long.
If we were able to track the rough last-executed time (or even just date) for each line (and that would likely need to be a configurable option, since it would require more memory), we could just leave it running, and we'd always be able to look at code and see if it's dead. The coverage statistics wouldn't really help us, since things that were run a year ago would be listed as 'covered', but I can imagine evolutions of behavior to resolve that as well, later :-)
It looks like they've got a working implementation (supporting only redis hash store), but I'd be happy to put in some extra time to make this a configurable behavior, and support it in additional stores.
danmayer
Is your feature request related to a problem? Please describe. I can recognize how many a line executed, but I cannot recognize when the line executed.
Describe the solution you'd like like this, displaying last posted datetime per line. "last posted time" is not "last executed time" precisely, but I think it is useful information.
PoC: https://github.com/FeLvi-zzz/coverband/pull/1
what do you think?
Describe alternatives you've considered none for now
Additional context none