microsoft / microsoft/winget-cli
Improve output for WinGet Configuration progress
Open
Nobody has claimed this yet.
Command-Configure
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
We got a PR in Dev Home to improve the UI output in Dev Home.
This is likely a good improvement to make in the WinGet CLI as well.
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 by reviewing the linked Dev Home pull request 912 to understand the intended progress UI improvement. The issue names no WinGet files, tests, or entry points, so first locate the WinGet Configuration progress-output path and define the expected CLI behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100