microsoft / microsoft/winget-cli
Identify supported installer scopes
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
The manifest should declare the supported install scopes. Many manifests do not specify scope for an installer. This could either be a top-level enumeration of supported scope or make the scope field required in the installer key in the manifest.
This could be similar to "Install modes" where the manifest can declare that "Silent", "Silent with Progress", and "Interactive" as supported install modes.
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 by reviewing the manifest schema and the existing implementation of install modes. Compare whether supported scopes belong in a top-level declaration or as a required installer field, then identify the manifest validation and test coverage that would need to accept and verify the chosen representation.
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
- Needs clarification
- Newbie friendliness
- 25/100