Sean Wheeler

@JamesWTruher Can you provide an opinion here?

@dkaszews @adityapatwardhan Can one of you file a docs issue for this change? Use https://github.com/MicrosoftDocs/PowerShell-Docs/issues/new?assignees=&labels=issue-doc-idea%2Cneeds-triage&projects=&template=03-change.yml

@joeyaiello A while back I fixed all of the broken HelpInfoUri values that I could. There are currently 4 modules that are broken: - ConfigDefender - This is a Windows...

PSReadLine is a known issue. I provided a workaround on the PowerShell team blog: https://devblogs.microsoft.com/powershell/updating-help-for-the-psreadline-module/ PowerShell TeamUpdating help for the PSReadLine module | PowerShell TeamUpdating help for the PSReadLine module...

@df1966 This is a known issue that there is no direct fix for. We blogged about this and there is a work around. See - https://devblogs.microsoft.com/powershell/updating-help-for-the-psreadline-module-in-windows-powershell-5-1/ - https://devblogs.microsoft.com/powershell/updating-help-for-the-psreadline-module/ PowerShell TeamUpdating...

@MaximoTrinidad the PSReadline issue is well known and documented. It will not be fixed in Windows until Server 2022. Please see - https://devblogs.microsoft.com/powershell/updating-help-for-the-psreadline-module-in-windows-powershell-5-1/ The other modules are known issues as...

@veleek There was a miscommunication from the PowerShell team. The fix for this is in 7.4-preview.1, not 7.3.

The request here is to support the metadata. It is up to the author to populate the information. This information will be used by the publishing platform.

Can you show an example of what you are talking about?

I am not sure what the impact of unsafe characters would be on `Get-Help` and `Update-Help`. The filename wouldn't match the true command name. This is a pattern that we...