Get-Help: parameter aliases are (again) missing from local help display with -Full and -Parameter #20787
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
Judging by MicrosoftDocs/PowerShell-Docs#1638 (comment), this was fixed at least at some point in PS Core, but the problem is back.
Only the online versions of the cmdlet help topics list parameter aliases such as -lp and -PSPath for -LiteralPath.
# With -Full
Get-Help Get-ChildItem -Full | Out-String -Stream | Select-String '^\s+-LiteralPath' -context 0, 9
# Parameter-individual
Get-Help Get-ChildItem -Parameter LiteralPathExpected behavior
> -LiteralPath <System.String[]>
Specifies a path to one or more locations. The value of LiteralPath is used exactly as it's typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. Single quotation marks tell PowerShell to not interpret any characters as escape sequences.
For more information, see about_Quoting_Rules (../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
Required? true
Position? named
Default value None
Accept pipeline input? True (ByPropertyName)
Aliases PSPath, LP
-LiteralPath <System.String[]>
Specifies a path to one or more locations. The value of LiteralPath is used exactly as it's typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. Single quotation marks tell PowerShell to not interpret any characters as escape sequences.
For more information, see about_Quoting_Rules (../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
Required? true
Position? named
Default value None
Accept pipeline input? True (ByPropertyName)
Accept wildcard characters? false
Aliases PSPath, LPActual behavior
The Aliases line is missing in both cases.
Error details
No response
Environment data
PowerShell 7.4.0Visuals
No response