microsoft / microsoft/winget-cli
`Update-WinGetPackage -WhatIf`: Installs the update instead of saying what it would do
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
If one starts Update-WinGetPackage -WhatIf
then it installs the update instead of saying what it would do
Steps to reproduce
Just start Update-WinGetPackage -WhatIf for any package
Expected behavior
Of course, as is always the case with PowerShell: A CmdLet only shows what it would do.
(Do we need to explain this to Microsoft? I wonder that Microsoft does not have unit-tests for default parameters.)
Actual behavior
If one starts Update-WinGetPackage -WhatIf
then it installs the update instead of saying what it would do
Environment
Windows Package Manager v1.8.1791
Windows: Windows.Desktop v10.0.19045.2006
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.23.1791.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the implementation of Update-WinGetPackage and its WhatIf handling, then reproduce the issue with Update-WinGetPackage -WhatIf for a package. Done means the command reports the intended update without installing it, while normal updates still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100