microsoft / microsoft/winget-cli-restsource
Improved architecture handling
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 317
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Description of the new feature / enhancement
Some packages offer a different "latest" version of an application based on the architecture supported.
When the WinGet client is communicating with a REST endpoint the communications should be optimized to deal with different versions for different architectures.
The default flow should provide a better customer experience for both the "install" and "upgrade" scenarios.
When a specific architecture is specified using arguments, the response should honor the architecture specified.
When the "download" flow is being used, there should be an affordance to download the latest versions for "all" architectures.
There may also be caveats when a specific version is requested as opposed to just the "latest" version.
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
The issue names no files, tests, or entry points, so first map the REST endpoint handling for install, upgrade, and download flows. Define how latest and specific-version requests should select architectures, including the explicit architecture argument and the option to download all architectures; done means those scenarios return the expected versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100