Skip to content
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

[Command Explorer] Configuration Options #1677

Open
wsmelton opened this issue Jan 1, 2019 · 2 comments
Open

[Command Explorer] Configuration Options #1677

wsmelton opened this issue Jan 1, 2019 · 2 comments
Labels
Area-Command Explorer Issue-Enhancement A feature request (enhancement). Up for Grabs Will shepherd PRs.

Comments

@wsmelton
Copy link

wsmelton commented Jan 1, 2019

Summary of the new feature

Have the ability to configure a few options for the command explorer:

  1. Filter modules, just exclusions

Anyone that uses AzureRM or the Az module has commonly found that majority of the "noise" in the command explorer for the ISE was taken up by that module. Having the ability to filter out the modules would allow users to more easily find modules they may want to work with in a particular workspace. (e.g. If I'm working on say something with dbatools then I don't need to see modules like AzureRm and Az in that list, because they may not pertain to the project.)

  1. Group By

As it stands the commands are listed by letter. I would like to be able to have them listed by module right off, it offers a more focused discovery on whatever project I may need to use a module. I can find that module listed faster and discover the commands around it.

Proposed technical implementation details (optional)

I would think having the filter ability would be having a configuration like powershell.cmdexplorer.filter and the value provided be comma separated list (much like the font setting in Code supports. So something like:

"powershell.cmdexplorer.filter": "'Az','AzureRm','Microsoft.PowerShell.Security'"

For the group by I would expect it only to support certain values, so it could start out by allowing group by feature for modules. If any additional ideas come up they just be setup as keywords that have to be provided based on what you want to group by. The default would be letters so it does not effect those that have gotten used to the current setup.

"powershell.cmdexplorer.listby": "letter"
"powershell.cmdexplorer.listby": "module"
"powershell.cmdexplorer.listby": "verb"
@SydneyhSmith SydneyhSmith added Issue-Enhancement A feature request (enhancement). Area-Command Explorer labels Jan 3, 2019
@SydneyhSmith
Copy link
Collaborator

@wsmelton thanks for this request, seems like a reasonable enhancement. The command explorer is a community driven feature, so I am marking it as "up for grabs", feel free to submit a pr 😄

@SydneyhSmith SydneyhSmith added the Up for Grabs Will shepherd PRs. label Jan 3, 2019
@corbob
Copy link
Contributor

corbob commented Jan 8, 2019

I've done up a proof of concept for an exclusion filter. The sorting one may take more thought, and might not be needed if we can get a search box.

I'll put together a PR and start to clean it up a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Command Explorer Issue-Enhancement A feature request (enhancement). Up for Grabs Will shepherd PRs.
Projects
None yet
Development

No branches or pull requests

3 participants