microsoft / microsoft/winget-cli
WinGet shouldn't require an additional command to enable configuration
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
As a user attempting to run a WinGet Configuration, I don't want to have to run a separate command to enable configuration.
The App Installer package (including WinGet) is defaulted to a "stub application" containing only WinGet package management. When a user with the stub package runs winget configure configuration.winget the command exits and the user is required to run winget configure enable.
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 handling for winget configure, especially the path used when the App Installer package is a stub application. Run winget configure configuration.winget in that package state and compare it with winget configure enable. Done means a configuration can be run without requiring the separate enable command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100