Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dotnet CLI should support search of NuGet packages on one or all configured sources #12891

Closed
saturley-hall opened this issue Aug 12, 2020 · 4 comments
Labels
cli-ux Issues and PRs that deal with the UX of the CLI (exit codes, log output, verbs/options, and so on)

Comments

@saturley-hall
Copy link

Issue
I would find it useful for the dotnet CLI to enumerate packages (and versions of packages) on a NuGet feed and enable searching of one or more NuGet feeds for keywords, tags, and names of a package.
The desired functionality is similar to the list command of nuget.exe, though hopefully

Proposed Solution
Add a dotnet nuget subcommand ls that has a structure somewhere between grep and and nuget list.
This provides the combined functionality of listing all packages or listing packages that match a user-defined search term which are available on one or more NuGet feeds

nuget ls [OPTION]... [-s PATTERN]... [SOURCE]...:

When passed with no SOURCEs all enabled sources are used and only the most recent Release version are returned.

  • -a, --all-versions flag specifies all versions available on the feed are returned sorted in descending order.
  • -i, --include-disabled flag specifies use of both enabled and disabled sources.
  • -s, --search-term option specifies one or more search terms which will be used to filter packages

When passed with one or more [SOURCE] parameters with the name of an established feed or a URL defining a feed those are the feeds from which packages are listed.

Method of Implementation
While this could be added as a dotnet core tool, and it is fairly similar to dotnet-search (and perhaps should be added there first), it feels like core functionality that should be supported by the CLI without adding a tool.

@baronfel baronfel added the cli-ux Issues and PRs that deal with the UX of the CLI (exit codes, log output, verbs/options, and so on) label Aug 26, 2022
@Frulfump
Copy link

Frulfump commented Mar 4, 2025

This was closed without a comment. Isn't this still relevant? I would like this feature at least.

@saturley-hall
Copy link
Author

Feel free to reopen.

@Frulfump
Copy link

Frulfump commented Mar 4, 2025

Sadly I don't have permission for that, or did you mean I should open a new issue? Any rationale for closing it that you could provide?

@baronfel
Copy link
Member

baronfel commented Mar 4, 2025

This actually exists today - the 'dotnet package search' command fills this gap. If there are features or enhancements desired to it, I'd suggest raining a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli-ux Issues and PRs that deal with the UX of the CLI (exit codes, log output, verbs/options, and so on)
Projects
None yet
Development

No branches or pull requests

3 participants