Repository navigation
Enhancement Request: Get-Verb -Group parameter #2527
Description
The Get-Verb cmdlet should include a -Group Parameter, or another means of filtering the list of approved verbs.
Steps to reproduce
Per Windows PowerShell 5.0 documentation, Get-Verb Syntax is:
Get-Verb [[-Verb] <string[]>] [<CommonParameters>]
Expected behavior
Get-Verb -Group <Common|Communications|Data|Diagnostic|Lifecycle|Other|Security>
Specifying a -Group Parameter would filter to show only the approved verbs in that Group.
Alternatively, Get-Verb could support a -Filter, or -Include and -Exclude parameter(s)
Actual behavior
Get-Verb enumerates the full list of approved verbs and their corresponding verb group, but does not provide a convenient way to filter and more easily view approved verbs
Environment data
Symptom appears consistent from PSVersions 3.0 - 5.0
Activity
iSazonov commentedon Oct 24, 2016
Bryan Dady (@bcdady) Thanks for the enhancement request.
Today
(get-verb).countreturn 98. Do you really think that this short list should be filtered? Could you give practical examples?I believe that this list is very short and stable. And that I would really expect from this cmdlet, this is a description of the verbs and groups.
jpsnover commentedon Oct 24, 2016
I like it!
kilasuit commentedon Oct 24, 2016
Not sure there is much need for this as its simple enough to just pipe to Where-Object in my opinion.
bcdady commentedon Oct 26, 2016
Ryan Yates (@kilasuit) Yes, except that with
| where {}, the admin / IT Pro needs to first know that Verbs are grouped, the names of the Groups they want to view verbs from. Strictly speaking, they could first invokeget-verb | select Group -Unique, and then try each of those Group names through| where {$_.Group -eq $group } | Out-Host -Paging. But why not make all that easier (especially newbies learning the ropes, not yet familiar with approved verbs. If the same results were possible via a parameter of the cmdlet, then an IT Pro can more simply tab through the available Groups, select the best option for their use case, and enumerate the list approved Verbs in that Group.iSazonov commentedon Oct 26, 2016
I do think that there isn't a cmdlet that is used less frequently:
Get-Verb
bcdady commentedon Oct 26, 2016
Ilya (@iSazonov) Perhaps after we make it more useful, it will be used more frequently.
iSazonov commentedon Oct 26, 2016
Give up! 😊
What do you say to add a brief description?
lzybkr commentedon Oct 26, 2016
There is little point in speculating on the usage.
I don't really see any downside to this proposal, it is a simple change to add and I can't see the any potential UX problems in the future, e.g. the cmdlet ending up with too many parameters.