microsoft / microsoft/winget-cli
WinGet Configuration clarifications regarding WinGet Settings
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
A WinGet Configuration should define the desired state.
This could conflict with WinGet Settings.
This needs to be clearly documented.
There are also interactions with pinning and "requirements" that we'll need to decide how to deal with.
In addition, more work needs to be done on the Microsoft.WinGet.DSC resource to support additional behaviors associated with other arguments that can be used to specify installation requirements:
- #3401
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 by reviewing the WinGet Configuration and WinGet Settings behavior, then examine the interactions with pinning and requirements described here and follow issue #3401. Done means documenting the desired-state relationship and deciding which additional installation-requirement behaviors Microsoft.WinGet.DSC must support.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100