`New-MarkdownCommandHelp` & `Export-MamlCommandHelp` commands create a parent folder with module name

[ArmaanMcleod]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest version
• Search the existing issues.

Steps to reproduce

I have some markdown files which I create in my ./docs/en-US folder using New-MarkdownCommandHelp.

When I run New-MarkdownCommandHelp it creates another parent folder with the module name inside like ./docs/en-US/<ModuleName>

Same happens with Export-MamlCommandHelp.

Workaround is to flatten the directory structure, but this is extra work. Is there another parameter to avoid this? I don't think any command should be creating parent folders and leave that to the user to decide.

Expected behavior

To output directly into the directory, I specify and create no extra parent folders.

Actual behavior

Creates parent directory with module name.

Error details

Environment data

Name                           Value
----                           -----
PSVersion                      7.5.4
PSEdition                      Core
GitCommitId                    7.5.4
OS                             Microsoft Windows 10.0.26100
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Version

1.0.1

Visuals

No response

[belibug]

Especially when output folder is provided, all files should be placed in the path provided without creating Parent folder with Module Name. Helps in CICD to know the absolute path beforehand.