-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
Pri3Priority - LowPriority - Low
Description
Note: This is posted a separate issue related to PowerShell/PowerShell#4716 per @SteveL-MSFT's request; this issue may go away, once all core cmdlets have the appropriate parameters consistently decorated with [SupportsWildcardsAttribute], assuming that the external help files are created by reflection.
Output from Get-Help -Parameter <param-name>, Get-Help -Full should consistently reflect whether a parameter supports wildcard patterns as arguments or not.
Currently, the free-form parameter description mentions wildcard support, while the list of properties describing the parameter does not; e.g.:
> Get-Help Get-Item -Parameter Path
-Path <String[]>
Specifies the path to an item. This cmdlet gets the item at the specified location.
Wildcards are permitted. # !! This is the ONLY indication that wildcards are supported.
This parameter is required, but the parameter name ("Path") is optional.
Use a dot (.) to specify the current location. Use the wildcard character (*) to specify all the items in the current location.
Required? true
Position? 1
Default value none
Accept pipeline input? true (ByValue, ByPropertyName)
Accept wildcard characters? false # !! Contradicts the above.
Metadata
Metadata
Assignees
Labels
Pri3Priority - LowPriority - Low