f0rt

Here is the version information: Name Value ---- ----- PSVersion 5.1.15063.674 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.15063.674 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 Is this...

We can. The problem is that we're getting reports from customer about this issue. If this is not going to be fixed I guess our PMs will address with a...

Sorry. I've uploaded wrong file. [Get-Test.md.txt](https://github.com/PowerShell/platyPS/files/2436788/Get-Test.md.txt) So the file uploaded above results in only 1 syntax item with 1 required parameter and 1 optional parameter which is not correct. It...

The problem with the single parameter set(as showed in the example md) is that the default parameter set may have only optional parameters and the second parameter set may have...

I see that PS has a problem too. I'm not sure how this is related to MD to MAML conversion since the markdown already contains 2 syntax items and the...

See my latest example that illustrates the problem correctly. The cmdlet has 2 parameter sets but the "Default" parameter set syntax item is not generated. [Get-Test.md.txt](https://github.com/PowerShell/platyPS/files/2455778/Get-Test.md.txt)

I've modified your example to create a repro script: ``` powershell function foo { param( [Parameter(ParameterSetName="Default")] [Parameter(ParameterSetName="p1")] [string]$bar, [Parameter(ParameterSetName="p1", Mandatory=$true)] [string]$foo ) } New-MarkdownHelp -Command foo -OutputFolder ./ New-ExternalHelp -Path...

Can you please take a look at the PR above that contains the fix?

Oh, I got it all wrong. :) I now see the problem in the code. Let me summarize: **Problem:** The "GatherSyntax()" doesn't have enough information to generate the correct syntax...

What about Option1?