The following metadata is shown on Gallery but missing on VS Client:
New metadata, not yet exposed even on Gallery
Also, I would add the package type (DotnetTool
, Dependency
, etc) to the registration API. This is useful if the client has a different UI based on the package's type. For example, the NuGet gallery has a different UI for installation instructions if the package is a dependency or a tool. Like @anangaur mentions below, this shouldn't show up on the Package Manager UI.
Also, we should consider including the source code's repository type to decide which icon to display.
Edited to clarify :)
We should revisit package type when we discuss Search by TFM experience. IMO different package types shouldn't even show up on PM UI.
Any updates on this?
Release Notes can be important at install/upgrade time.
Don't quite understand why this is not getting implemented? I don't think it's a hard change. Fields like release notes are important to MSFT internal customers (devs) and even more so to external customers / users.
@chgill-MSFT I made this an Epic since it's pretty broad. I know there's ongoing work to spec out Readme's. Can you please link those here (directly or to the Epic) so I can understand the full scope? Thank you!
Most helpful comment
Release Notes can be important at install/upgrade time.