microsoft / microsoft/winget-cli
Validate manifest fields are present in the correct file
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
Validate command does not check whether optional fields are present in the correct file.
For example, you can define optional installer-specific fields like Scope, InstallerType in the locale file and optional locale fields like ReleaseNotesUrl, PurchaseUrl in the installer file and winget validate would still report Manifest validation succeeded.
For better semantics, these changes should not be allowed / discouraged by winget validate.
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 validate command and trace the manifest validation entry point for installer and locale files. Done means misplaced optional fields such as Scope, InstallerType, ReleaseNotesUrl, and PurchaseUrl are rejected or discouraged while valid manifests continue to validate successfully.
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
- Needs clarification
- Newbie friendliness
- 35/100