microsoft / microsoft/winget-cli
Add ability to filter `winget list` and `winget search` commands by install scope (user/machine)
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
It would be wonderful to be able to filter the list and search commands to restrict to packages that were (for list) or can-be (for search) installed specifically as a user or machine package.
Proposed technical implementation details
Add a --Scope command line parameter to the WinGet CLI in ListCommand.cpp and SearchCommand.cpp. Use the preexisting Execution::Args::Type::InstallScope enumeration (which is already used and validated in the install command).
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 in ListCommand.cpp and SearchCommand.cpp, then compare how the install command uses and validates Execution::Args::Type::InstallScope. Trace the list and search command entry points to determine how a --Scope value should restrict installed or available packages. Done means both commands accept the parameter and apply the requested user or machine scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100