microsoft / microsoft/winget-cli
Additional AppsAndFeaturesEntry fields for ARP Matching
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
In the AppsAndFeaturesEntry, there are additional fields which could be used for ARP Matching if they were added to the manifest and were populated by package maintainers. Any available ARP fields could be added to the manifest to improve ARP Matching
Proposed technical implementation details
AppsAndFeaturesEntries:
- DisplayName: # This already exists
Publisher: # This already exists
DisplayVersion: # This already exists
ProductCode: # This already exists
UpgradeCode: # This already exists
InstallerType: # This already exists
HelpLink: # This is new
UrlInfoAbout: # This is new
URLUpdateInfo: # This is new
EstimatedSize: # This is new
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 AppsAndFeaturesEntry manifest definition and the ARP Matching code path. Check how existing fields such as DisplayName, Publisher, DisplayVersion, ProductCode, UpgradeCode, and InstallerType are populated and consumed. Add support for the proposed HelpLink, UrlInfoAbout, URLUpdateInfo, and EstimatedSize fields, then verify that ARP Matching can use the available values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100