microsoft / microsoft/winget-cli
Relaxing the character limit on the PackageIdentifier property
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
Hey folks,
I recently ran into the PackageIdentifier length cap when creating a manifest for an application I'd released on the Microsoft Store. My intention was to keep the identifier the same between Winget and the MS Store, but it was a few characters too long.
Is there a possibility of relaxing the character limit for this property? It's fairly easy to run into the 32 character limit with a useful and descriptive package name.
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 schemas/JSON/manifests/v1.6.0/manifest.singleton.1.6.0.json at the PackageIdentifier length constraint linked in the issue. Trace how that constraint is consumed, then verify that a manifest with a longer useful identifier is accepted without breaking existing validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100