microsoft / microsoft/winget-cli
Allow searching errors without `0x`
Open
Nobody has claimed this yet.
Area-Output
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
When using winget error and the hex code, it would be nice if WinGet could automatically detect that the input is a Hex code and not require the 0x
Example: winget error 8A15000D
Proposed technical implementation details
No response
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 winget error command entry point and trace how its error-code argument is parsed. Verify the command recognizes 8A15000D as the same hex code as 0x8A15000D, while preserving existing behavior for inputs that already include 0x.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100