joelverhagen
commented
4 years ago /cc @karann-msft @ryuyu
Today, our nuget.org experiences related to package type are:
- Toggling "command palette" behavior based on package type.
DotnetTool:
Template:
- Normal dependency:
- Full options defined in DisplayPackage.cshtml
- API-only: search by package type and returning package type(s) in the response body
- This is an API-only feature right now and is still in the works and therefore undocumented.
- This was implemented to support a forth-coming .NET CLI feature: https://github.com/dotnet/sdk/issues/3808
I think showing the information in search results is probably the easiest next step, followed by enabling filtering by package type in the nuget.org UI. We would just need to work out what it should look like and which package types we should show.
We allow any package type that meets the character restrictions (i.e. package type names use the same pattern as package IDs) to be uploaded so it's not clear we would want to show any possible package type in the search UI since we don't know the scenarios around 3rd party package types. I think it would be probably fine to show them all but we should think it through.
Other note: the NuGet client APIs don't support this new search protocol yet (see https://github.com/NuGet/Home/issues/8915).
Is your feature request related to a problem? Please describe.
When searching for packages, it's not discernible from the search results what types of packages I've found. In this screenshot, for example, the first result is a library while the second is a tool:
Describe the solution you'd like
Ideally, the different package types would be visually distinct from one another.