WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
I was testing the winget configuration validation and intentionally supplied a bad resource name by adding a 'Z' at the end of name expected it to fail.
Winget should report that the resource Microsoft.Windows.Developer/ShowSecondsInClockZ does not exist and suggest likely names Microsoft.Windows.Developer/ShowSecondsInClock
Brief description of your issue
I was testing the
winget configuration validation
and intentionally supplied a bad resource name by adding a 'Z' at the end of name expected it to fail.However, the CLI still output
This makes me think there is something that implicitly skips unrecognized resources.
Steps to reproduce
See logs
Run validation command such as
Expected behavior
Winget should report that the resource
Microsoft.Windows.Developer/ShowSecondsInClockZ
does not exist and suggest likely namesMicrosoft.Windows.Developer/ShowSecondsInClock
Actual behavior
winget reports
Environment