Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
sdwheeler opened this issue May 18, 2023 · 1 comment
Open

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

sdwheeler opened this issue May 18, 2023 · 1 comment

Comments

@sdwheeler
Copy link
Contributor

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
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sdwheeler