-
-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filter with date #64
Comments
Hi! Thanks for opening this issue. Yeah! It’s a great idea. It’s actually a pending TODO (you can see it on the README.) It hasn’t yet been incorporated due to the ‘technical difficulty’ that you yourself mention. Just as you said, calculating the last modification in the node_modules file isn’t enough, we have to analyse the rest of the project’s files, since this is what will really let us know how long it’s been since it was last worked on. We’ve detailed the process here in case someone reads this and would like to start working on this :) |
I'm working on the feature of add "last working date of the project" atribute to results so when it is ready, this issue will be able to continue going forward |
Hey!
|
Feature Request.
I would save a lot of time if I could automate the process of filtering and deleting the folders. Then I could automate it with my backup plan, i.e. first delete node_modules of old projects, then borgbackup.
Describe the solution you'd like
another parameter which lets you filter (and/or delete) after a given number of days passed since the project has been touched. We could discuss whether the tool should look after the
package.json
or the youngest file in thenode_modules
folder (or the youngest file in the parent directory, aka project directory, of thenode_modules
folder).You could use it like so:
It then shows only all projects which are older than 50 days
Describe alternatives you've considered
using
find
..The text was updated successfully, but these errors were encountered: