Proxy cmdlet parameter maps don't match current available parameters in v3 module

PowerShell / PowerShellGet

This module provide functions used with PowerShellGet v3 to provide compatibility with scripts expecting PowerShellGet v2

MIT License

49 stars 13 forks source link

Proxy cmdlet parameter maps don't match current available parameters in v3 module #28

Closed sdwheeler closed 1 year ago

sdwheeler commented 1 year ago

Summary of the new feature / enhancement

For example, the proxy cmdlet for Update-Script removes the Force parameter from $PSBoundParameters before calling Update-PSResource. However, Update-PSResource has a Force parameter, so it should not be remove.

Proposed technical implementation details (optional)

Make sure the parameter maps are accurate for all proxy cmdlets.