-
Notifications
You must be signed in to change notification settings - Fork 644
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
Always show supported frameworks for packages #4598
Comments
Even so, what is shown there can actually be misleading, since this is about dependency groups, not about supported frameworks. This can be different, e.g. if for some lower frameworks there are no dependencies, or they are the same for multiple compatible versions. |
Agree. We should look at adding this functionality along with "Context aware search" feature that aims to add more such metadata around to package details page. May be both sets of information are required. We need to think through the right way to surface the info without confusing the users. cc: @karann-msft can you link this to the proposed feature? |
We've shipped a Frameworks tab on the package details page. This shows all package asset frameworks (frameworks directly expressed by assets in the package) and calculated frameworks (implicit support via TFM mappings). This was tracked by #4843 and is now resolved. Go try it out if you haven't already 😃. The ability to filter package search by TFM or by supported framework is tracked by #3098. If you feel that what you're describing is now implemented yet, please feel free to open a new issue with details! Thanks! |
Today NuGet.org shows the frameworks only if there are dependencies in the packages.
Twitter thread: https://twitter.com/imperugo/status/899901309788225540
The text was updated successfully, but these errors were encountered: