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

Filter Account owned Packages by deprecated vs non-deprecated #10142

Open
michael-hawker opened this issue Aug 20, 2024 · 3 comments
Open

Filter Account owned Packages by deprecated vs non-deprecated #10142

michael-hawker opened this issue Aug 20, 2024 · 3 comments
Labels
feature-request Customer feature request Triaged

Comments

@michael-hawker
Copy link

michael-hawker commented Aug 20, 2024

Related Problem

Looking at the https://www.nuget.org/account/Packages view of packages on our account, we have 128 in varying states. I need to update some of them to point to others...

While I can sort, I can't filter this list to look for a common root. Or I can't separate it out based on deprecated or non-deprecated packages like I can with listed/unlisted packages...

The Elevator Pitch

It'd be nice as a package owner to have a greater ability to view a subset of packages that I need to work on either by:

  • filtering out by a search term within the page
  • by removing entirely deprecated packages from my view (like I can with unlisted ones)

Additional Context and Details

No response

@michael-hawker michael-hawker added the feature-request Customer feature request label Aug 20, 2024
@erdembayar erdembayar changed the title [Feature]: Filter Account Packages List Filter Account owned Packages by deprecated vs non-deprecated Aug 20, 2024
@erdembayar
Copy link
Contributor

Probably we could have more filters other than deprecated.

cc @JonDouglas

@michael-hawker
Copy link
Author

Should this issue track multiple types of filters or should we have an issue for each one?

As filtering the list down based within the name of the package would be helpful too.

@erdembayar
Copy link
Contributor

Should this issue track multiple types of filters or should we have an issue for each one?

As filtering the list down based within the name of the package would be helpful too.

Just 1 would be suffice, you can edit the original text description to add more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Customer feature request Triaged
Projects
None yet
Development

No branches or pull requests

2 participants