microsoft / microsoft/winget-cli

Search after install finds no match

Open
#581 1 comment 6 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

Perform a search if an install has no results

If I execute winget install nightingale I get an error message. "No package found matching input criteria"

The correct command would have been winget install "Nightingale REST Client"

If an install doesn't find a match, then the client should perform a search.
If only one result matches, the user could be prompted to install the package that was found (if only one is found).

Proposed technical implementation details (optional)

First Example
winget install nightingale
No package found matching input criteria.
Executing winget search nightingale
Name Id Version Source
---------------------------------------------------------------------------------
Nightingale REST Client 43891JeniusApps.NightingaleRESTAPIClient Latest msstore
Would you like to install [Y/N]?

Second Example
winget install terminal
No package found matching input criteria.
Executing winget search terminal
Name Id Version Match Source
----------------------------------------------------------------------------------------------
IO Ninja tibbo.ioninja 3.14.4 Tag: terminal winget
Windows Terminal Microsoft.WindowsTerminal 1.3.2651.0 Tag: terminal winget
Terminus Eugeny.Terminus 1.0.120 Tag: terminal winget
Alacritty Alacritty.Alacritty 0.4.3 Tag: terminal winget
bottom Clement.bottom 0.4.7 Tag: terminal winget
Windows Terminal Preview Microsoft.WindowsTerminalPreview 1.4.2652.0 Moniker: Terminal winget
SecureDNS.Terminal Texnomic.SecureDNS.Terminal 0.3-alpha winget
Fluent Terminal 53621FSApps.FluentTerminal Latest msstore
TerminAll BEDKOAS.TerminAll Latest msstore
Windows Terminal Microsoft.WindowsTerminal Latest msstore
Windows Terminal Preview Microsoft.WindowsTerminalPreview Latest msstore
>

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 by reproducing the winget install nightingale and winget install terminal examples and inspect the install command's no-match path. Determine where search results and prompts are handled. Done means a no-match install can search the input and handle single or multiple results as described; add coverage for both examples.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.