Should use of unmapped parameters cause a Warning message?

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

Should use of unmapped parameters cause a Warning message? #29

Open sdwheeler opened 1 year ago

sdwheeler commented 1 year ago

Summary of the new feature / enhancement

For example, the proxy cmdlet for Update-Script takes *Proxy and ProxyCredential cmdlets. Those parameters are discarded because they are unsupported by Update-PSResource.

Should this cause a warning message?
What is the compatibility impact of a Warning message?
Can/Should we add a WhatIf parameter so users can get a warning in the WhatIf output?

Proposed technical implementation details (optional)

No response

sdwheeler commented 1 year ago

Maybe Warning is not the right choice, but adding information to the Verbose stream would help people understand what is happening in the proxy cmdlet.