Cannot execute mock for Get-PackageSource cmdlet

[nohwnd]

In order to fix Get-PackageSource cmdlet, another level of indirection was introduced which broke other things.

Original issue and PR:
#1308
#1317

Issue it caused and revert PR:
#1519
#1528

[nohwnd]

@renehernandez I reverted the change, because from what I understand it only affects Get-PackageSource cmdlet which is not a blocker for release. If you'd have time please take a look.

[splatteredbits]

Any way to work around this issue? I'm trying to mock Get-PackageSource in a test:

Describe 'Pester' {
    It 'mocks Get-PackageSource' {
        Mock -CommandName 'Get-PackageSource'
        Get-PackageSource
    }
}

and I get this error:

Pester v5.7.1

Starting discovery in 1 files.
Discovery found 1 tests in 14ms.
Running tests.

Running tests from 'C:\Users\ajensen\Downloads\MockGetPackageSource.ps1'
Describing Pester
  [-] mocks Get-PackageSource 122ms (108ms|14ms)
   ParameterBindingException: Parameter set cannot be resolved using the specified named parameters.
   at <ScriptBlock>, C:\Users\ajensen\Downloads\MockGetPackageSource.ps1:9

[splatteredbits]

My workaround was to create a parameter-less global function, then remove that function after the test:

        function global:Get-PackageSource 
        {
            param(
            )
        }

        try
        {
            $mockLocation = $script:mockLocation
            Mock -CommandName 'Get-PackageSource' -MockWith {
                [pscustomobject]@{ Name = 'NuGet.org'; Location = $mockLocation; ProviderName = 'NuGet' }
            }

            # Test implementation
        }
        finally
        {
            if ((Test-Path -Path 'function:Get-PackageSource'))
            {
                Remove-Item -Path 'function:Get-PackageSource'
            }
        }

[splatteredbits]

Maybe add switch to Mock that tells Pester not to try to re-implement the function parameters?

[nohwnd]

Tried to have another look on this, but I will have to debug it deeply to figure out a fix that does not break other stuff.

I think your workaround is as close as you can get right now (one change could be to inject the function just into the places where you need it).