Add --all option for dotnet list package

[erdembayar]

Currently customer have to make 2 separate queries to find out both outdated and vulnerable packages with dotnet list package, instead we need --all which shows all deprecated, vulnerable, and outdated top level and transitive packages

#11446 (comment)

I'm including screenshot given GH is not good at tracking comments/discussion.

[JonDouglas]

I think #11549 should handle this situation. I don't think an "-all" flag frankly makes sense.

[JonDouglas]

I also just don't think list commands are going to scale well enough with this much information being outputted.

Say you have a project with 30 dependencies. Those might have 6 transitive dependencies each. Now produce output 3x and your console is not readable as a human.

[erdembayar]

I also just don't think list commands are going to scale well enough with this much information being outputted.

Say you have a project with 30 dependencies. Those might have 6 transitive dependencies each. Now produce output 3x and your console is not readable as a human.

Yes, it doesn't make sense for plain output, but could be used as shortcut for json output instead of putting all possible combination.

[nkolev92]

The arguments, --vulnerable, --outdated are filters and change the output format.

--all does not make it clear what the format of the output should be, or whether it should be an AND or an OR operation between these filters.