microsoft / microsoft/winget-cli
Make a TUI for WinGet
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
I had originally been thinking of WinGet 2.0 having a breaking change for an interactive experience. Recently I've been thinking of a TUI.
@shanselman suggested a new argument like "--tui".
This would mean no breaking change necessary for a more interactive experience!
We'd want some settings and arguments to make sure when someone default to TUI, that scripts and other things can still function correctly. We already have "--disable-interactivity" to "Disable interactive prompts".
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 with the WinGet CLI argument handling and the existing --disable-interactivity behavior. Define the TUI scope, the proposed --tui argument, and settings that preserve script behavior; no files or tests are identified in the issue, so completion criteria need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100