microsoft / microsoft/winget-cli
Improved UX for Import
Open
Nobody has claimed this yet.
Area-Output
Command-Import
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
When I am importing a collection of packages,
- I would like to see the name of the package being imported
- I would like to know the version being imported (if specified)
- I would like to know which architecture is being installed
If the version to be imported is specified and a newer version is installed, we need to make a determination of what to do in that case.
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. Start by tracing the collection import flow in the WinGet CLI and determine where package name, requested version, and architecture can be reported. Define the behavior for a specified version when a newer version is already installed, then identify tests covering both the import display and version-selection decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100