Code blocks not allowed in DESCRIPTION

[jazzdelightsme]

(and I think they should be allowed)

Steps to reproduce

In a ## DESCRIPTION section, add a fenced code block (I think that's what they're called: when you have a line with three backticks, then some lines of code, then another line with three backticks).

Expected behavior

The New-ExternalHelp command should succeed.

Actual behavior

The New-ExternalHelp command throws an error:

ForEach-Object : Exception calling "NodeModelToMamlModel" with "1" argument(s): "E:\temp\blah\Send-Feedback.md:17:(41) '```
    PS\> Send-Feedback "messsage"
    or, ...'
 Expect Heading"
At C:\Users\blah\Documents\PowerShell\Modules\platyps\0.14.0\platyPS.psm1:1564 char:22
+     $markdownFiles | ForEach-Object {
+                      ~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [ForEach-Object], MethodInvocationException
+ FullyQualifiedErrorId : HelpSchemaException,Microsoft.PowerShell.Commands.ForEachObjectCommand

Environment data

v0.14.0

[jazzdelightsme]

(same problem with the ## NOTES section)

[vors]

I think this is mostly dupe of #422, although there is no error in that report.
The question is about schema. Can you elaborate what are the use cases and why you don't want to move them into the EXAMPLES section?

[jazzdelightsme]

The scenario is that I'm trying to migrate some existing hand-maintained MAML (yuck) content. The team has some "preformatted text" in these areas that needs to not get messed up by markdown rendering. ("Code blocks" are not just for code.)

And I'm not in front of the right machine right now, but I believe the reason I ran into the ## NOTES one is that I was trying to use a codeblock to compensate for the fact that I hit the same problem with a numbered list. I.e. in their NOTES section, they had something like

1. Remember first thing.
2. Second thing.
3. Blah blah more.

But it got rendered terribly, like "1. Remember first thing. 2. Second thing. 3. Blah blah more.", which is not acceptable.

This problem is blocking me from moving this help content.

[vors]

PlatyPS has a number of heuristics to correctly parse out the numbered lists and bullet points automatically. It’s unfortunate that they didn’t work for your, but I do t think that solution is to use codeblocks. As a workaround, you can manually enter blank lines between the items in the list. A more scalable and more time consuming way is to provide a small crafted sample of such maml file, so we can find out why the heuristic didn’t work.

[jazzdelightsme]

Thanks @vors. Would just the foo.dll-Help.xml file be sufficient? I could send that to you privately (you could email the address on my profile to let me know how).

[vors]

I'd appreciate if you can spend some time and trim it down to something small that can be publicly shared and replace all sensitive information with some placeholders. I don't think that I personally will work on it any time soon, but there is a community of people and also folks from PS team who may help out with it.

My goal is to facilitate the unblocking of scenarios people report. It's particularly enlightening when in a conversation in a GitHub issue, we get enough context collaboratively that reporter of the issue can become a contributor and fix it themselves. That happens rarely, but it's always a treat.
Let's aim for that, when possible - I think this issue is a great candidate for such outcome.

[jazzdelightsme]

Okay, below is the input (old, hand-maintained) MAML for just one command. There is a lot of terribleness, but in particular, pay attention to the "NOTES" section (<maml:alert> in the input). After converting MAML to MD (via New-MarkdownHelp), it looks pretty bad. But even when I manually reformat the MD, I can't get good output when converting back to MAML (via New-ExternalHelp).

Note that I think the problem is more than just not detecting the list... More fundamentally I don't think it is reasonable to prevent people from putting pre-formatted content into DESCRIPTION and NOTES sections. This is a complete dealbreaker for me.

Code

<?xml version="1.0" encoding="utf-8" ?>
<helpItems xmlns="http://msh" schema="maml">

  <command:command
 xmlns:maml="http://schemas.microsoft.com/maml/2004/10"
 xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10"
 xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" >
    <command:details>
      <command:name>Test-Thingy</command:name>
      <command:verb>Test</command:verb>
      <command:noun>Thingy</command:noun>
      <maml:description>
        <maml:para>Executes tests on the connected thingy.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>
        The Test-Thingy cmdlet creates Snazzy test content from either a ABC query file or
        a test command line and executes it on the current thingy.
        The cmdlet will use all PowerShell variables named '$Snazzy_*' as parameters
        in the submission being executed (minus the 'Snazzy_').

        Example: $Snazzy_Foo in PS = [Foo] in Snazzy

        The command will deploy packages when there are packages specified in ABC job or TestThingy definition.
      </maml:para>
      <maml:para>
        FooShell supports executing TestThingy files (-testthingy), and ListOTests files (-listotests),
        ABC files (-qqq), and Testpasslist files (-testpasslist).

        Note: FooShell does not currently support multiple ListOTests files and does not support executing qqq
        files within a listotests. When a listotests includes ABC jobs, they are skipped and
        only the TestThingy files are executed.
      </maml:para>
      <maml:para>
        Examples:

        Run a listotests with an absolute path: test-thingy -listotests
        \\foobuilds\release\[branch]\[buildstring]\amd64fre\build\prebuilt\Test\amd64\fre\file.listotests

        Run a testthingy with a relative path: test-thingy -testthingy
        Test\amd64\fre\file.testthingy -PackageRootPath
        \\foobuilds\release\[branch]\[buildstring]\amd64fre\build\prebuilt

        Run a testthingy or listotests without package search paths when FooShell is launched in Razzle
        (BUILDROOT and BUILDROOT/Mc.[RazzleBuildArch] will be used as PackageRootPaths)
        Test-Thingy -testthingy test.testthingy
        Test-Thingy -listotests test.listotests

        More examples, use get-help test-thingy -full
      </maml:para>
    </maml:description>
    <maml:alertSet>
      <maml:title>Ordering of paths for package search</maml:title>
      <maml:alert>
        <maml:para>
          The following are the location of packageroots which will be searched in order when arguments are being used
          1. BUILDROOT (if FooShell is launched in razzle)
          2. Galactic test definition directory when full path to testthingy is specified.
          3. AlternateRoots
          4. PackageRootPaths and its build slabs if the path is an official build.
          5. Build slabs from OnThingy command if the image on the thingy is an official image.
        </maml:para>
      </maml:alert>
      <maml:title>Default package search path when FooShell launched in Razzle</maml:title>
      <maml:alert>
        <maml:para>
          If Test-Thingy is being called without additional arguments, BUILDROOT and BUILDROOT/Mc.[RazzleBuildArch] will be used as PackageRootPaths.
          In additional, for official image on the connected thingy, build slabs of the image on the thingy will also be used in additional to BUILDROOT

          Example:
          Test-Thingy -qqq filename.qqq
          Test-Thingy -testthingy test.testthingy
          Test-Thingy -listotests test.listotests
        </maml:para>
        <maml:para>
          For Galactic Tests, if a full path to Galactic Test definition (testthingy) is passed in without additional argument, current directory where testthingy is found
          will be used as part of PackageRootPaths.

          Example: Test-Thingy -testthingy c:\test\dir1\test.testthingy
        </maml:para>
      </maml:alert>
    </maml:alertSet>
    <command:syntax>
      <command:syntaxItem>
        <maml:name>Test-Thingy</maml:name>
        <command:parameter required="true" >
          <maml:name>ListOTestsFileName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ListOTestsFilter</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PreferredSearchPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>TimeoutMinutes</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageRootPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>OnThingy</maml:name>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestToolsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>AlternatePackageRoots</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DeployPackageMacroOverride</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageCache</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>SkipBuildAutoResolution</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideReport</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ListOnly</maml:name>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestArchitecture</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestSelect</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
      </command:syntaxItem>
      <command:syntaxItem>
        <maml:name>Test-Thingy</maml:name>
        <command:parameter required="true" >
          <maml:name>TestThingyFileName</maml:name>
          <command:parameterValue>int[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>TimeoutMinutes</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageRootPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>OnThingy</maml:name>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestToolsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>AlternatePackageRoots</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DeployPackageMacroOverride</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageCache</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>SkipBuildAutoResolution</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ExecutionProfile</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ListOnly</maml:name>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestArchitecture</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestSelect</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
      </command:syntaxItem>
      <command:syntaxItem>
        <maml:name>Test-Thingy</maml:name>
        <command:parameter required="true" >
          <maml:name>JobIds</maml:name>
          <command:parameterValue>int[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DataStore</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>RunOffline</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DependencySearchPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageRootPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>OnThingy</maml:name>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestToolsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>AlternatePackageRoots</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageCache</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>SkipBuildAutoResolution</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>Iterations</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>TestReport</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideReport</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideOutput</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideTests</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsUri</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ListOnly</maml:name>
        </command:parameter>
        <command:parameter>
          <maml:name>ThingyLogPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>NoDeploy</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>CopyUnchanged</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>RunLiftedTasksAsBrian</maml:name>
        </command:parameter>
      </command:syntaxItem>
      <command:syntaxItem>
        <maml:name>Test-Thingy</maml:name>
        <command:parameter required="true" >
          <maml:name>FileName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>Arguments</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>FileDependencies</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>FileOutputs</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ExpectedExitCode</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>TimeoutMinutes</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>RunOffline</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DependencySearchPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageRootPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>AlternatePackageRoots</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestToolsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DeployPackageMacroOverride</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageCache</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsUri</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>Iterations</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideOutput</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideReport</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideTests</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>NoDeploy</maml:name>
        </command:parameter>
        <command:parameter>
          <maml:name>ThingyLogPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>SkipBuildAutoResolution</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ListOnly</maml:name>
        </command:parameter>
      </command:syntaxItem>
      <command:syntaxItem>
        <maml:name>Test-Thingy</maml:name>
        <command:parameter required="true" position="0" >
          <maml:name>QqqFileName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>RunOffline</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DependencySearchPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageRootPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>AlternatePackageRoots</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestToolsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DeployPackageMacroOverride</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageCache</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsUri</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>Iterations</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideOutput</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideTests</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>NoDeploy</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>OnThingy</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ListOnly</maml:name>
        </command:parameter>
        <command:parameter>
          <maml:name>ThingyLogPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>RunLiftedTasksAsBrian</maml:name>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestArchitecture</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
      </command:syntaxItem>
      <command:syntaxItem>
        <maml:name>Test-Thingy</maml:name>
        <command:parameter required="true" position="0" >
          <maml:name>QqqFileName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="true" >
          <maml:name>TemplateWorkflowFileName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="true" >
          <maml:name>TemplateParameterName</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>RunOffline</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DependencySearchPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageRootPaths</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>AlternatePackageRoots</maml:name>
          <command:parameterValue>string[]</command:parameterValue>
        </command:parameter>
        <command:parameter required="false">
          <maml:name>TestToolsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>DeployPackageMacroOverride</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>PackageCache</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ResultsUri</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>Iterations</maml:name>
          <command:parameterValue>int</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideOutput</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>HideTests</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>NoDeploy</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>OnThingy</maml:name>
        </command:parameter>
        <command:parameter>
          <maml:name>ThingyLogPath</maml:name>
          <command:parameterValue>string</command:parameterValue>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>SkipBuildAutoResolution</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>RunLiftedTasksAsBrian</maml:name>
        </command:parameter>
        <command:parameter required="false" >
          <maml:name>ListOnly</maml:name>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <command:parameter required="true" position="0" >
        <maml:name>ListOTestsFileName</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The path of the .listotests file to be executed
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="true" position="0" >
        <maml:name>TestThingyFileName</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The path of the single .TestThingy file to be executed
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="true" position="0" >
        <maml:name>JobIds</maml:name>
        <command:parameterValue>string[]</command:parameterValue>
        <maml:description>
          <maml:para>
            ABC Job Ids to be executed
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="true" position="0">
        <maml:name>FileName</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The name or path of the executable to run as the test.
            Non-rooted paths are treated relative to the current thingy directory.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="true" position="0" >
        <maml:name>QqqFileName</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The path of the ABC query file to evaluate for tests to execute.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" position="1">
        <maml:name>Arguments</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The arguments to pass to the test process.
            The entire arguments list must be passed in as a single parameter to PowerShell,
            so the list must be passed inside single quotes.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>Packages</maml:name>
        <command:parameterValue>string[]</command:parameterValue>
        <maml:description>
          <maml:para>
            The list of extra packages to deploy to the thingy prior to execution.
            Packages are identified by their file name minus the extension.

            This parameter is a PowerShell array, so it must be properly formatted as such.
            Examples:
            (one item array)  cmdlet -arg "item1"
            (one item array)  cmdlet -arg "item1,item2"

            (two item array)  cmdlet -arg "item1","item2"
            (two item array)  $items = "item1","item2"
            cmdlet -arg $items

            Run 'help about_arrays' for more details on creating PowerShell arrays.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>FileDependencies</maml:name>
        <command:parameterValue>string[]</command:parameterValue>
        <maml:description>
          <maml:para>
            The list of extra dependency files to copy to the thingy prior to execution.

            This parameter is a PowerShell array, so it must be properly formatted as such.
            Examples:
            (one item array)  cmdlet -arg "item1"
            (one item array)  cmdlet -arg "item1,item2"

            (two item array)  cmdlet -arg "item1","item2"
            (two item array)  $items = "item1","item2"
            cmdlet -arg $items

            Run 'help about_arrays' for more details on creating PowerShell arrays.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>FileOutputs</maml:name>
        <command:parameterValue>string[]</command:parameterValue>
        <maml:description>
          <maml:para>
            The list of extra output files to copy back from the thingy after execution.

            This parameter is a PowerShell array, so it must be properly formatted as such.
            Examples:
            (one item array)  cmdlet -arg "item1"
            (one item array)  cmdlet -arg "item1,item2"

            (two item array)  cmdlet -arg "item1","item2"
            (two item array)  $items = "item1","item2"
            cmdlet -arg $items

            Run 'help about_arrays' for more details on creating PowerShell arrays.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>ExpectedExitCode</maml:name>
        <command:parameterValue>int</command:parameterValue>
        <maml:description>
          <maml:para>
            The exit code expected to be returned by the test process.
            If a different exit code is returned, it will cause the test to fail.
            The default value is 0.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>TimeoutMinutes</maml:name>
        <command:parameterValue>int</command:parameterValue>
        <maml:description>
          <maml:para>
            The amount of time (in minutes) to wait for the test process to exit.
            If the test process does not finish within this time, it will get an Expired result.
            The default value is based on the test harness used to run the test.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>RunOffline</maml:name>
        <maml:description>
          <maml:para>
            When specified will run the test(s) offline, meaning the thingy connection
            will be severed for the duration of each execution workflow run.
            By default all tests are run online.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>NoDeploy</maml:name>
        <maml:description>
          <maml:para>
            When specified will run the test(s) without copying any packages to the thingy.
            Note: This is true of offline tasks as well, so specifying -NoDeploy with -RunOffline
            will cause a failure, unless the packages required for running offline tasks
            have been previously deployed.

            These packages are:
            Contoso.Widget.Test.TestInfra.Snazzy.Common
            Contoso.Widget.Test.TestInfra.Snazzy.ThingyTaskManager
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>OnThingy</maml:name>
        <maml:description>
          <maml:para>
            When specified, will try to find the build share for the build installed on the thingy to deploy packages and copy
            test collateral. (Family Internal Only)

            Note: If both PackageRootPath and OnThingy are specified and PackageRootPath is from an official build, only PackageRootPath and build slabs extracted from the path will be used.
            AlternatePackageRoots can be used with OnThingy when additional search paths are needed.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>DependencySearchPaths</maml:name>
        <command:parameterValue>string[]</command:parameterValue>
        <maml:description>
          <maml:para>
            The list of directories to use when resolving file dependency paths.

            This parameter is a PowerShell array, so it must be properly formatted as such.
            Examples:
            (one item array)  cmdlet -arg "item1"
            (one item array)  cmdlet -arg "item1,item2"

            (two item array)  cmdlet -arg "item1","item2"
            (two item array)  $items = "item1","item2"
            cmdlet -arg $items

            Run 'help about_arrays' for more details on creating PowerShell arrays.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>PackageRootPaths</maml:name>
        <command:parameterValue>string[]</command:parameterValue>
        <maml:description>
          <maml:para>
            The root paths in which to look for the specified packages to deploy.

            If specified, this value should be the binary root of a thingy build,
            ie. the "Binaries" folder for official builds. The paths will also be used for build slab search using
            ONS unless -SkipBuildAutoResolution is set.
            If the value is not specified, the %GREEN_TREE% or %BINARY_ROOT% environment variables
            will be used as the package root (GREEN_TREE takes precedence).


            Ex. Test-Thingy ... -PackageRootPaths "\\Build\release\Mercury\Branch\BRANCH.8422.9725.20120625-1506\MC.armfre\Binaries"
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>SkipBuildAutoResolution</maml:name>
        <maml:description>
          <maml:para>
            Whether to query Ocelot Notification System (ONS) for Build Slabs
            By default, ONS will be used to query for Build Slabs
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>AlternatePackageRoots</maml:name>
        <command:parameterValue>string[]</command:parameterValue>
        <maml:description>
          <maml:para>
            A collection of alternate package root paths to be examined for installed packages.
            Unlike the PackageRootPaths, alternate package root paths need not have a "prebuilt"
            sub-directory.

            Note: Alternate package root paths are examined in the order they are specified in
            the command line, then the paths specified in the PackageRootPaths. The first root to
            contain the package is the one that is used.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>TestToolsPath</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The location to search for DeployTest.exe and related deployment tools.

            In most cases, the parameter can be left unassigned. When not specified, the version of the tool installed with FooShell will be used.
            In the case it cannot be resolved, the registry will be examined for installed
            TestCentral content, and the specified TestCentral folder will be used as the test tools path.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>DeployPackageMacroOverride</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The macro that needs to be overridden and the path that the macro should now be set to.
            Ex. TestShare=\\graybucketlabs\securestorage\mercury\testdata
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>PackageCache</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The path to where you'd like to store/retrieve cached packages on your local machine. This is
            only beneficial when pointing your package root path to a build share/POD, and is not only
            not useful when using %BINARY_ROOT% but can present stale packages. Recommended path
            is something like D:\PackageCache. Note: caches are stored per branch, and the same
            Package Cache can be used for all branches and builds.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false">
        <maml:name>ListOTestsFilter</maml:name>
        <maml:description>
          <maml:para>
            This optional parameter can be used to filter the list of TestThingys and ABC Jobs in the ListOTests and its references to a specific set.
            Supported attributes are @AbcJob.GUID, @TestThingy.Name, @TestThingy.FilePath and @TestThingy.Profile.
            Wildcards are supported to enable selection of multiple items.

            Ex.
            test-thingy -listotests my.listotests -ListOTestsFilter "@AbcJob.GUID='177f47a8-a15e-4066-97d0-a24ebcef16ac'"
            test-thingy -listotests my.listotests -ListOTestsFilter "@TestThingy.Name='MyTestThingy.testthingy' AND @TestThingy.Profile='Performance'"
            test-thingy -listotests my.listotests -ListOTestsFilter "@TestThingy.FilePath='MyTeam\Performance*.testthingy'"
            test-thingy -listotests my.listotests -ListOTestsFilter "@AbcJob.GUID='177f47a8-a15e-4066-97d0-a24ebcef16ac' OR  (@TestThingy.Name='MyTestThingy.testthingy' AND @TestThingy.Profile='Performance'"
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false">
        <maml:name>PreferredSearchPaths</maml:name>
        <maml:description>
          <maml:para>
            To run a ListOTests in FooShell you must be aware of ListOTests search paths. ListOTests search paths are an ordered list of absolute directory paths that are used to resolve each ListOTests or TestThingy reference in a ListOTests by prepending them to the corresponding FilePath property.
            FooShell will try to infer a list of listotests search paths from the context, but you may provide a prioritized list by using -PreferredSearchPaths. These search paths could be used to find ListOTestss and TestThingys before searching under any inferred search paths.

            The list of preferred search paths may be separated by commas if unquoted or by commas,spaces or semicolon if quoted.
            Ex

            test-thingy -listotests my.listotests -PreferredSearchPaths "C:\foo,D:\bar;D:\baz D:\quxx"
            test-thingy -listotests my.listotests -PreferredSearchPaths C:\foo,D:\bar

            You can also use the -searchpaths shorthand alias. Visit https://example.com/wiki/Test-thingy_(FooShell)#Executing_a_ListOTests for more detailed information.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>ResultsPath</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The root path where test execution results are stored,
            in the following sub-folders for each run:
            &lt;Execution Session&gt;\&lt;Time Stamp&gt;\&lt;Workflow&gt;\&lt;Task&gt;
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="true" >
        <maml:name>ResultsUri</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            An additional Snazzy URI where test execution results are sent.
            The value is transport agnostic and the format is: &lt;Host&gt;:&lt;Port&gt;
            It will be converted into the Snazzy transport specific format by FooShell.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>Iterations</maml:name>
        <command:parameterValue>int</command:parameterValue>
        <maml:description>
          <maml:para>
            The number of times to execute the tests in the query, default is once.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>HideReport</maml:name>
        <maml:description>
          <maml:para>
            When specified will not show the test results report after execution has finished.
            The report XML file will still be generated in the results directory.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>ListOnly</maml:name>
        <maml:description>
          <maml:para>
            When specified will just list the tests in the query and not execute anything.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="true" >
        <maml:name>TemplateWorkflowFileName</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The full path to a template workflow (a workflow containing an IncludeWorkflow primitive
            with the FilePath parameterized with the TemplateParameterName).
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="true" >
        <maml:name>TemplateParameterName</maml:name>
        <command:parameterValue>string</command:parameterValue>
        <maml:description>
          <maml:para>
            The name of the parameter used in the template workflow.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>HideOutput</maml:name>
        <maml:description>
          <maml:para>
            Whether to hide raw output from the test process during execution.
            By default the output will be displayed in a separate console window.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>HideTests</maml:name>
        <maml:description>
          <maml:para>
            Whether to hide real-time test case data from the console.
            By default test case data is parsed during execution and displayed
            in the PowerShell console.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter>
        <maml:name>ThingyLogPath</maml:name>
        <maml:description>
          <maml:para>
            The fully qualified path to a file where to save the output from the thingy. This parameter is only
            available when using Exec-Thingy synchronously. Within a single open/close-thingy session
            you can continue to make Exec-Thingy calls to the same log file, and thingy output
            will be appended to the end. However, if you switch to a different log file,
            or if the session ends, any additional re-directs to a previous log file
            will cause the log to be recreated, wiping all previous content.

            Ex.
            Exec-Thingy ... -dlog "MyLog.txt"
            Exec-Thingy ... -dlog "MyOtherLog.txt"
            Exec-Thingy ... -dlog "MyLog.txt"  // Will overwrite previous content in MyLog.txt
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false">
        <maml:name>ExecutionProfile</maml:name>
        <maml:description>
          <maml:para>
            Sets the execution profile that will be used during the TestThingy execution.

            Ex.
            test-thingy -testthingy TestThingyWithExecutionProfiles.testthingy -ep "Name of Profile"
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false" >
        <maml:name>SkipBuildAutoResolution</maml:name>
        <maml:description>
          <maml:para>
            Skip ONS query for build slabs which is extracted from PackageRootPaths or build on the thingy when using OnThingy option.
            Ex.
            Deploy-Thingy .... -PackageRootPaths ... -SkipBuildAutoResolution
            Test-Thingy ... -PackageRootPaths ... -SkipBuildAutoResolution
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false">
        <maml:name>TestArchitecture</maml:name>
        <maml:description>
          <maml:para>
            Architecture being tested. Valid values are "amd64", "arm", "arm64", "arm64.arm" "arm64.x86", "x86" or "wow64".

            When specified for wow architectures, both architecture-specific and native packages will be deployed.
            If not specified, default to deploy native packages only based on the package root path.
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false">
        <maml:name>TestSelect</maml:name>
        <maml:description>
          <maml:para>
            The 'select' query for filtering and executing only specific tests from a TestThingy, or TestThingys contained in the listotests specified.
            If not specified, by default, all the tests in the TestThingy (or TestThingys contained in a ListOTests) are executed, while obeying
            ExecutionProfile specified, if any, for the TestThingy(s).

            If an ExecutionProfile which already contains a /select (or /name) is provided for the TestThingy file, the filter provided through TestSelect
            would take precedence over the ExecutionProfile's /select (or /name), since TestSelect's filter is appended last to HJKL's arguments.
            HJKL discards the /select (or /name) statements preceding the last /select (or /name) it encounters.

            TestThingy plugins, however, if present are evaluated at last when executing the workflow, so they would override the filter provided through
            TestSelect.

            If a testpasslist containing an execution filter is provided, it would replace all the existing execution parameters of the TestThingys the
            testpasslist contains, and the TestSelect filter would be appended to the end of that replaced execution parameter from the testpasslist.

            Ex.
            test-thingy -listotests my.listotests -TestSelect "@Name='foo*'"
            test-thingy -testthingy my.testthingy -TestSelect "@Name='foo*' or @Priority > 3"
            test-thingy -testthingy my.testthingy -TestSelect "@Architecture='x86'" -ep profile1
            test-thingy -testthingy my.testpasslist -TestSelect "@Name='*myfootest*'"
          </maml:para>
        </maml:description>
      </command:parameter>
      <command:parameter required="false">
        <maml:name>TestName</maml:name>
        <maml:description>
          <maml:para>
            The 'name' filter for filtering and executing only specific tests from a TestThingy, or TestThingys contained in the listotests specified.
            If not specified, by default, all the tests in the TestThingy (or TestThingys contained in a ListOTests) are executed, while obeying
            ExecutionProfile specified, if any, for the TestThingy(s).

            If an ExecutionProfile which already contains a /select (or /name) is provided for the TestThingy file, the filter provided through TestName
            would take precedence over the ExecutionProfile's /select (or /name), since TestName's filter is appended last to HJKL's arguments.
            HJKL discards the /select (or /name) statements preceding the last /select (or /name) it encounters.

            TestThingy plugins, however, if present are evaluated at last when executing the workflow, so they would override the filter provided through
            TestSelect.

            If a testpasslist containing an execution filter is provided, it would replace all the existing execution parameters of the TestThingys the
            testpasslist contains, and the TestName filter would be appended to the end of that replaced execution parameter from the testpasslist.

            Ex.
            test-thingy -testthingy my.testthingy -TestName "*myfootest*"
            test-thingy -testthingy my.listotests -TestName "*allfootests*"
            test-thingy -testthingy my.testpasslist -TestName "*myfootest*"
          </maml:para>
        </maml:description>
      </command:parameter>
    </command:parameters>
    <command:parameter required="false" >
      <maml:name>RunLiftedTasksAsBrian</maml:name>
      <maml:description>
        <maml:para>
          When specified, executable tasks in ABC jobs that are set to run under the currently logged on user story with lift
          (e.g. the "run this task as lifted when JKL is enabled" checkbox is checked in Atlas Studio) will be run under the paint
          context instead.  This is useful for running legacy ABC jobs on editions such as QWERTY where the default logged in story is
          not running with creamy or wispy privileges.

          Ex.
          Test-Thingy ... -qqq ... -RunLiftedTasksAsBrian
          Test-Thingy ... -jobid ... -RunLiftedTasksAsBrian
        </maml:para>
      </maml:description>
    </command:parameter>
    <command:examples>
      <command:example>
        <maml:title>----------  EXAMPLE 1  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute listotests with absolute path to .listotests</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -listotests \\foobuilds\release\[branch]\[buildstring]\amd64fre\build\prebuilt\Test\amd64\fre\file.listotests</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 2  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute testthingy with relative path to .testthingy</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -listotests Test\amd64\fre\file.testthingy</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 3  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute qqq file on connected thingy using official build on thingy</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -qqq [path to qqq file] -onthingy </dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 4  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute qqq file on connected thingy using official build on thingy</maml:para>
        </dev:remarks>
        <dev:code>Test-Thingy -qqq [path to qqq file] -PackageRootPath \\foobuilds\release\[branch]\[buildstring]\[architecture]</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 5  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute qqq file on connected thingy using official build on thingy</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -qqq [path to qqq file] -PackageRootPath \\build\release\[release]\[branch]\[buildstring]\[architecture]\binaries </dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 6  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute qqq file on connected thingy using official build on thingy</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -qqq [path to qqq file] -PackageRootPath \\build\release\[release]\[branch]\[buildstring]\[architecture]\binaries -SkipBuildAutoResolution</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 7  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute qqq file on connected thingy using official build on thingy</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -qqq [path to qqq file] -PackageRootPath \\build\release\[release]\[branch]\[buildstring]\[architecture]\binaries -onthingy</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 8  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute qqq file on connected thingy using official build on thingy</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -qqq [path to qqq file] -PackageRootPath \\build\release\[release]\[branch]\[buildstring]\[architecture]\binaries -onthingy</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 9  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute Galactic Test</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy [relativepath to PackageRootPath]\test.testthingy -PackageRootPath \\build\release\[release]\[branch]\[buildstring]\[architecture]\binaries</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 10  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute Galactic Test using full path to galactic test file description</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy c:\test\test\test.testthingy -PackageRootPath \\build\release\[release]\[branch]\[buildstring]\[architecture]\binaries</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 11  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute Galactic Test with build from thingy</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy [relativepath to PackageRoot]\test.testthingy</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 12  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute Tests using ABC Job Id</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy -jobid 12345</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 13  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute Galactic Test for wow64 test architecture</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy [relativepath to PackageRootPath]\test.testthingy -PackageRootPath \\foobuilds\release\[branch]\[buildstring]\amd64fre\build\prebuilt -TestArch wow64</dev:code>
      </command:example>
      <command:example>
        <maml:title>----------  EXAMPLE 14  ----------</maml:title>
        <dev:remarks>
          <maml:para>Execute ListOTests</maml:para>
        </dev:remarks>
        <dev:code> Test-Thingy [relativepath to PackageRootPath]\test.listotests -PackageRootPath \\foobuilds\release\[branch]\[buildstring]\amd64fre\build\prebuilt</dev:code>
      </command:example>
    </command:examples>
  </command:command>
</helpItems>

[vors]

Awesome, really appreciate your effort!
I reformatted your last comment to hide the code under a collapsible section (just learned this trick today :D), so it's going to be easier to have the conversation in the same issue going forward.

[vors]

Regarding using the code blocks for pre-formatted content, I'd agree that this is an annoying limitation. Code blocks have special meaning in the Parameters and the Examples, so just allowing using them freely in all other sections would make the UX somewhat inconsistent. But that could be an ok tradeoff, I guess.

[fourpastmidnight]

I've run into this too. I don't understand why this isn't allowed, more specifically, why platyPs treats Code blocks "special" such that when it sees them, it assumes that it must be in a parameter block or example section. The parser probably keeps around some state about what it's doing, so one of the things it ought to know is what section it's currently processing via the most recent header that's been parsed. So, if the parser is in a DESCRIPTION section, it ought to know that any code blocks which are encountered should just be considered text.

To bolster my point, I have found a "workaround" to this. It's not great, but it works. Instead of using ```powershell, use ```text. PlatyPS does not complain about this.

Extra credit: write a PowerShell script for your build process which finds code blocks in sections of the Markdown file for which PlatyPS doesn't allow code blocks, update them to text as described above. Then generate the help--and lastly, revert the changes (git co -- ./docs/*.md or git reset --hard, depending on the circumstances.). It seems a little silly to have to resort to such antics for something as basic as this that the parser ought to be able to handle.

[fourpastmidnight]

UPDATE/CORRECTION

I was incorrect. My "workaround" does not work. The place where I thought it was working actually happened to be in a parameter block.

[theJasonHelmick]

@jazzdelightsme Thank you for reporting this issue. This is planned for our upcoming V2 release to allow code blocks in the description section.