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

Show missing metadata on VS PM - package details #7957

Closed
Tracked by #7284
anangaur opened this issue Apr 4, 2019 · 10 comments
Closed
Tracked by #7284

Show missing metadata on VS PM - package details #7957

anangaur opened this issue Apr 4, 2019 · 10 comments
Assignees
Milestone

Comments

@anangaur
Copy link
Member

anangaur commented Apr 4, 2019

The following metadata is shown on Gallery but missing on VS Client:

New metadata, not yet exposed even on Gallery

  • Signing information
  • ReadMe
@loic-sharma
Copy link
Contributor

loic-sharma commented Apr 16, 2019

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 :)

@anangaur
Copy link
Member Author

We should revisit package type when we discuss Search by TFM experience. IMO different package types shouldn't even show up on PM UI.

@emulicus
Copy link

emulicus commented Nov 7, 2019

Any updates on this?

@JVimes
Copy link

JVimes commented Jul 30, 2020

Release Notes can be important at install/upgrade time.

@jerrylzy
Copy link

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.

@donnie-msft
Copy link
Contributor

@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!

@nkolev92
Copy link
Member

Looks like the majority of the issues listed, with the exceptions of release notes are completed.

Maybe this can be closed in favor of a dedicated release notes issue?

@nkolev92
Copy link
Member

Team Triage: Closing this issue as nearly all individual tasks have been completed.
For release notes, please follow: #1203.

@mwpowellhtx
Copy link

Is there a (successful) resolution to this as per the OP request? I'd like to relay Owner metadata as well. Thank you...

@nkolev92
Copy link
Member

@mwpowellhtx That's actively being worked on: #12501.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests