microsoft / microsoft/winget-cli
Group all Boolean fields in Installer Manifest
Open
Nobody has claimed this yet.
Area-Manifest
Breaking-Change
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
Instead of having individual boolean fields, it would be nicer for purposes of authoring / reading / suggesting edits to have a single Flags field that was an Enum of all the boolean values. If present the boolean is true, if absent it is false.
Proposed technical implementation details
Example:
Flags:
- downloadCommandProhibited
- requireExplicitUpgrade
- archiveBinariesDependOnPath
- installerAbortsTerminal
- installLocationRequired
- displayInstallWarnings
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
No files, tests, or entry points are named. Start by locating the Installer Manifest definition and its existing individual boolean fields, then trace how those fields are authored, read, and used for edit suggestions. Done means the boolean values are represented by the proposed Flags enum without losing the documented true/false behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100