microsoft / microsoft/winget-cli
`Get-WinGetConfiguration` default `-Path` to what `winget config` points to
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
Microsoft.WinGet.Configuration v1.8.1911-alpha: https://www.powershellgallery.com/packages/Microsoft.WinGet.Configuration/1.8.1911-alpha
Instead of requiring input for -Path on Get-WinGetConfiguration, default to the WinGet config default path, also opened by winget config?
%LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
If you accept this change this should also be applied to other cmdlets getting or setting WinGet config.
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-WinGetConfiguration cmdlet and compare its current -Path behavior with the path opened by winget config: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json. Check the other WinGet configuration cmdlets as well, since the request proposes consistent defaults. Done means Get-WinGetConfiguration no longer requires -Path and related configuration operations use the same default.
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
- 45/100