-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Last workspace usage: show and filter #134
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-technical proof- Each result is assigned the modification time of the most recent file in the workspace (parent directory of the node_module) and the days that have elapsed will be displayed
eb6f0ce
to
ace3e01
Compare
…l into feat/last-project-usage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This expected feature adds one more property to each result: The last time the project in which the node_module (or specified target directory) is located was worked on.
This is done by scanning all files in the parent directory for the modification date of the most recent one.
--sort date
is also added.Why not look directly at when the node_module was modified?
Because the developer may not have done npm i for a long time but is actively working on the project so I think it is more useful to look at the modification date.
Why not just look at the modification date of the directory?
According to this web, that property is only updated when a file is added, deleted or renamed.
This close #76, close #64