microsoft / microsoft/winget-cli
Add install scope parameter to the `Get-WinGetPackage` commandlet
Open
Nobody has claimed this yet.
Issue-Feature
- 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
Adding onto #6046 , add support to the PowerShell commandlet to down to the WinGet CLI, any Scope parameter specified.
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 Get-WinGetPackage commandlet entry point and review the related context in issue #6046. Trace how the commandlet communicates with the WinGet CLI, then verify that a specified Scope value reaches the CLI and is covered by the relevant commandlet tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100