Please add a 'bulk' unlisting facility
Wagnerp opened this issue · comments
Hi! Thanks for reporting this feature/bug/question!
Please keep / fill in the relevant info from this template so that we can help you as best as possible.
Type (choose one):
- Feature request
NPE version: 6.0.64+c118e46e01
OS version: Windows 11 22621
Installed from: Microsoft Store
In case of a FEATURE REQUEST:
Currently, there is no easy way to 'bulk' unlist packages. The reason why someone may need to use this is to retire old packages, yes, you can do this individually, but what if you have 100+ versions? Tools such as this are great, but complex to use.
What do you find hard to do with Nuclear? Is there things that are confusing or poorly explained? Is there any features you would add?
Hi @loic-sharma
Thanks for responding, it's a great tool, but maybe a GUI version would help. Also, the *-*
switch/option is not in the application documentation. I would possibly add the number of packages found for the specified package i.e. (x/y).
Also, the
*-*
switch/option is not in the application documentation.
The *-*
documentation is at the bottom of this table: https://github.com/loic-sharma/nuclear#version-ranges
Do you find the phrasing confusing? Do you have any recommendations?
I would possibly add the number of packages found for the specified package i.e. (x/y).
That's a good idea, I opened loic-sharma/nuclear#1 to track this. Feel free to send a pull request if you'd like!
Also, nuclear will output JSON if you add the --output json
option. You can use this JSON and PowerShell to count the number of results. For example, here's how to count the number of Newtonsoft.Json versions:
(nuclear list newtonsoft.json --output json | ConvertFrom-Json).Length
The - documentation is at the bottom of this table: https://github.com/loic-sharma/nuclear#version-ranges
The documentation when you use the -h
switch needs to reflect all available commands, if you want I could look into this?
Also, I don't know if this is possible, but is there a way to inform the user how long they can use their API key again to carry on operations?
The documentation when you use the
-h
switch needs to reflect all available commands, if you want I could look into this?
Yup go for it, that's a great idea 👍
is there a way to inform the user how long they can use their API key again to carry on operations?
It might be possible, but I'd have to do a bit more research. API key expiry is determined entirely by the NuGet server; the NuGet protocol doesn't have anything related to API key expiry. However, the NuGet server's responses can contain warnings such as expiring API keys. Nuclear should report those warnings.