Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

1. Make a module, and set Prefix to 'Test'
2. Import-Module MyTestModule -Prefix ''
3. All commands will still have test prefix

This is because the prefix test checks for IsNullOrEmpty instead of just null.

            bool usePrefix = !string.IsNullOrEmpty(prefix);

As such it is impossible to override the prefix which affects the ability to write pester tests on modules, etc. and use the original function names so that things like references and go to definition work in IDEs like vscode.

Workaround

Make a secondary manifest that references the same module but does not have the prefix specified.

Expected behavior

Commands without prefix

Actual behavior

Commands have default prefix

Error details

No response

Environment data

PS 7.2.1

Visuals

No response