Sean Wheeler

I just tested this with PlatyPS 0.14.2 and got the same result.

@adityapatwardhan > * parameterValueGroup I tested this and it is the accepted values. I can't find anything that uses `valueFrom`.

Our current standard is to document all parameters for all supported providers. The documentation indicates which provider the parameter comes from. We need a way for PlatyPS to discover the...

@chrisda Can you test this with https://github.com/PowerShell/platyPS/releases/tag/v2.0.0-preview1. They may have been fixed.

There are 2 issues here: 1. Update-Markdown help get the current help text from Get-Help (which gets it from MAML). The conversion to MAML remove hyperlinks and some other formatting...

This issue is fixed in PR #497.

I think we need to add `-WithModulePage` to the `Update-MarkdownHelp` cmdlet. Or create a new parameter `-UpdateModulePage` to update/create the module page only.

I think you need to escape the trailing asterisk as well. For example: ``` ## DESCRIPTION One \* asterisk seems to work ok. There should be \* two \* asterisks...

Our current style says that Examples should use the `powershell` label but syntax blocks should not.

Repro steps: 1. Run Get-Command -Syntax on Update-MarkdownHelp 2. Run New-MarkdownHelp -Command Update-MarkdownHelp 3. Compare results Example: ```powershell PS C:\Git\PS-Other\platyPS> gcm Update-MarkdownHelp -Syntax Update-MarkdownHelp [-Path] [[-Encoding] ] [[-LogPath] ] [[-Session]...