Description
Summary of the new feature
Have the ability to configure a few options for the command explorer:
- 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.)
- 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"