microsoft / microsoft/winget-cli

Improved architecture handling for Microsoft.Rest type source(s)

Open
#5,145 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

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.

Related to:

Proposed technical implementation details

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the requested install, upgrade, and download behaviors in this issue, then read the related winget-cli-restsource issue 276 for context. Define how architecture-specific responses, explicit architecture arguments, all-architecture downloads, and specific-version requests should behave before identifying implementation and test locations. Done means these scenarios have agreed behavior and coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
api, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.