microsoft / microsoft/winget-pkgs
`Manifest-Metadata-Consistency` not considering root nodes
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
In the above PR, the Manifest-Metadata-Consistency label was applied for
=== manifests\f\Fly-io\flyctl\0.2.2 ===
Missing Properties value based on version 0.1.76:
NestedInstallerFiles
However, the commit did have NestedInstallerFiles, it was just placed at the root node instead of the installer node
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 linked pull request and the manifests\f\Fly-io\flyctl\0.2.2 path. Trace the Manifest-Metadata-Consistency check to see how it compares root and installer nodes, then reproduce the missing NestedInstallerFiles report with these manifests. Done means root-level properties are considered and valid manifests no longer receive this inconsistency label.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100