Adds deprecation links in PM UI

[dominoFire]

Bug

Fixes: NuGet/Home#10996

Regression? Last working version: No

Spec: https://github.com/NuGet/Home/blob/8fb8d219a76b99c2a3ce79f8364c946283d4a19b/proposed/2021/VSdeprecationfeature.md

Description

Adds three messages in PM UI:

• More Info: Takes you to the package details URL
• Alternate package link: it's an internal link that triggers a search in PM UI for the alternate package ID
• Deprecation message with no alternate package: When there is no alternative package, PM UI shows a deprecation

Demos

LInk in Package list

Link in Details pane

From Installed tab

PR Checklist

• PR has a meaningful title

• PR has a linked issue.

• Described changes

• Tests

  • Automated tests added: 2 new tests. Accessibility Insights test pass
  • [ ] Test exception
  • [ ] N/A

• Documentation

  • [ ] Documentation PR or issue filled
  • N/A: not needed. only in Release notes

Accessibility Tests

Test in Package List

Test in Details Pane

Known issues

This PR is affected by NuGet/Home#11055 ; that can be fixed separately.

[nkolev92]

All of this looks pretty reasonable, but I don't have great understanding about why it works just yet.

Did we consider the fact that alternate package metadata has a version range included as well?

[kartheekp-ms]

I think Alternate package link is not required in the list of packages tab because a warning icon is displayed anyway. Clicking on the package, user will see a deprecated message along with alternative package id.

[jebriede]

I think Alternate package link is not required in the list of packages tab because a warning icon is displayed anyway. Clicking on the package, user will see a deprecated message along with alternative package id.

@kartheekp-ms The link provides the user with a shortcut to the alternative package without having to click on the package to see the details so it saves them clicks. Since this code is complying with the design spec that resulted after user studies and was under review and approved by stakeholders and the UX board, I would recommend keeping it in the code.

[chrisraygill]

This is awesome! I do have a few questions though -

When you click on the alternative package link, is there a way to only show that package in the package list rather than initiating a regular search for the ID? It seems weird that we surface a full list of search results when the alternative package is a specific package.

I know for nuget.org packages, we can use "PackageId: " to get a single result. That's what I use in my proposal for VS package deep links: NuGet/Home#11047

The drawback is that it only works for nuget.org packages. That being said, I'm not sure it's likely that a user would have another feed that supports deprecation, but maybe @joelverhagen and @loic-sharma might know better.

Regardless of how we do it, I think this would be a much better experience if we only surfaced the specific alternative package. AFAIK It's not necessarily even guaranteed that searching for an exact ID will surface the ID matched package as the first result.

For reference:

• NuGet.org search filters/syntax: https://docs.microsoft.com/en-us/nuget/consume-packages/finding-and-choosing-packages#search-syntax

Also, if you click on the alternative package link from the Installed or Updates tab, does it go to the Browse tab?

[dominoFire]

All of this looks pretty reasonable, but I don't have great understanding about why it works just yet.

Did we consider the fact that alternate package metadata has a version range included as well?

@nkolev92 I tried including the version on search boxes, but, nuget.org shows no results. That's why i'm only using package ID.

[dominoFire]

This is awesome! I do have a few questions though -

When you click on the alternative package link, is there a way to only show that package in the package list rather than initiating a regular search for the ID? It seems weird that we surface a full list of search results when the alternative package is a specific package.

I know for nuget.org packages, we can use "PackageId: " to get a single result. That's what I use in my proposal for VS package deep links: NuGet/Home#11047

The drawback is that it only works for nuget.org packages. That being said, I'm not sure it's likely that a user would have another feed that supports deprecation, but maybe @joelverhagen and @loic-sharma might know better.

Regardless of how we do it, I think this would be a much better experience if we only surfaced the specific alternative package. AFAIK It's not necessarily even guaranteed that searching for an exact ID will surface the ID matched package as the first result.

For reference:

• NuGet.org search filters/syntax: https://docs.microsoft.com/en-us/nuget/consume-packages/finding-and-choosing-packages#search-syntax

Also, if you click on the alternative package link from the Installed or Updates tab, does it go to the Browse tab?

@chgill-MSFT Yes, it switches to Browse tab to look for packages.

Also, added packageid: to the search query. See images above