felipecaputo/git-project-manager

Support for wildcards in settings

Opened this issue · 0 comments

Is your feature request related to a problem? Please describe.
Refreshing the project list will often be slow if you haven't excluded every possible folder that may not contain a project. Without constant trial-and-error, you can't be certain you've excluded every folder.

Describe the solution you'd like
If the settings could support wildcards (such as the use of an asterisk *), there would be no need to do as much trial-and-error.

As an example, my current configuration contains the following:

"gitProjectManager.ignoredFolders": [
	".buildtools",
	".git",
	".settings",
	".spigotTestEnv",
	".vscode",
	".metadata",
	"__pycache__",
	"node_modules",
	"target"
]

Note: The above example is definitely missing some folders, but I can't remember every folder I want to exclude - this is my current configuration.

With wildcard support, it could be simplified to the following:

"gitProjectManager.ignoredFolders": [
	".*",
	"__*",
	"node_modules",
	"target"
]

Obviously, the examples above are very specific to my setup, but they are just examples 🙂.

Describe alternatives you've considered
A possible alternative to wildcards is... regex (Cue the violent screams).
Obviously, many people hate regex, however, it is still somewhat useful and would be a lot more powerful, although a lot less readable, than wildcards.

If this were to be considered, it would most-likely need some sort of escape sequence or setting to prevent unsuspecting users from accidentally inserting incorrect regex.

Additional context
This request is both to simplify and speed-up project searching, as it can take quite a long time if you've unknowingly allowed, as an example, a .git folder to be searched, or a node_modules folder.