-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add depth limit configuration option #2
Comments
Version 0.1.5 released with maxDepthRecursion and ignoredFolders config. I hope it will help you. |
Thanks for this, but I didn't see any performance boost. Looking at master I see the https://github.com/felipecaputo/git-project-manager/blob/master/src/gitProjectLocator.js#L53 Also, I think the max depth might work better if the search didn't have to recurse into the |
@martinpengellyphillips Sorry for that, I forgot that vcse publishs the local code instead of commited code. I Will fix that ASAP. And I will make the . |
Solved in 0.1.6. Sorry again @martinpengellyphillips, but now i think it is working fine |
Thanks for the quick update! Since updating to 0.1.6 the extension breaks for me with the following error:
I'll pull master locally and try to debug this further unless it is something you have seen already? |
In debug the error is not happening, I'm trying to figure it out. Any help is welcome |
VSCE does not manage well dependencies of dependencies :( I've figured it out in the worst way, but fixed now in 0.1.9 Sorry for the inconvenience @martinpengellyphillips |
Works! Thanks. One thing about max depth - I think it would be best if the max depth check is inclusive rather than the current exclusive (now that the return (maxDepth > 0) && ((currentDepth - initialDepth) > maxDepth); to return (maxDepth > 0) && ((currentDepth - initialDepth) >= maxDepth); This would then ensure that the common case of projects directly under projects base path is handled efficiently. Thanks again! |
Nevermind my last comment - max depth does work as expected! I was just expecting more of a performance boost, but I see it is actually |
What do you think about get the origin being optional? There isn't a real necessity for that, it was just an idea of handling cases with projects with the same name but, the label is the path itself so, we can let the repo origin configurable. |
Yeah - I think that would make sense. For me, the main thing about this extension was to reuse the fact I have On that note, it might be good to also consider putting the project name first and then the path after (perhaps like you had origin).
This would make the most important information (project name) more visible. I guess doing that could also help with filtering if name is considered first and then you can narrow down based on path name. So in the following (contrived) example, you would only have to type
|
@martinpengellyphillips I've added the configuration to disable the check remote origin, sorry for taking too much time but last sprint was hard to finish I've forgot the option to show project in the start of the quick pick, I will open a new issue for that and address that in 0.1.11 |
Thanks @felipecaputo ! This works perfectly - with |
Consider adding a way to limit the search depth (configuration option?) in order to improve performance for large folders.
The text was updated successfully, but these errors were encountered: