snipsco / snips-issues

Feel free to share your bugs with us.
14 stars 5 forks source link

[Console] Resources batch deletion #187

Closed Psychokiller1888 closed 4 years ago

Psychokiller1888 commented 5 years ago

Is your feature request related to a problem? Please describe. I have about 800 intents on my console, 40 assistants, 1k+ slots and dunno how many skills. All that because of the userless app creation we created and tested endlessly. I've run out of mouse left clicks trying to delete all that and I'm just thinking about making a new account

What are the use cases of this feature Adding a button on each tabs on the console (Skills, Intents, Slots) to delete all at once. This feature even has a second good point, allowing people to remove their data at once if they wish so. I know that published resource cannot be deleted.

Describe the solution you'd like Adding buttons to "Delete all"

Describe alternatives you've considered Buying a cheap mouse, sitting on my index for 30 minutes to numb it and click for 2 days to delete all of them. Or a mouse bot, but the console doesn't always react the same so sometimes it clicks before the nodals have open etc etc

Additional context Related to https://github.com/snipsco/snips-issues/issues/37

pocketjoso commented 5 years ago

I'm still a bit curious about the details of this. Is it really ~ delete all (within a resource group)? Won't there be some resources that you will want to keep? Is "delete all" sufficient, or do you need to be able to exclude some items from the batch deletion job?

Psychokiller1888 commented 5 years ago

Well, if you're motivated you can add a select all button, have some check box on all resources spawn and let us unselect those that we want to keep. I don't need it to be honest at the moment, as I need to just empty an account, without spending 2 days to programatically do it :)

pocketjoso commented 5 years ago

I just think it's a bit of an extreme case otherwise. If you really want to delete all creating a new account seems like the easiest solution.

Psychokiller1888 commented 4 years ago

this is what I'm talking about:

https://puu.sh/EuJ94.png

Imma waste my mouse deleting this.... Same for apps, assistants and intents

pocketjoso commented 4 years ago

Sorry for repeating my question but if you really intend to reset your account, would it not be easier to create a new account, than clearing one resource type after another? Or even that we introduced a "reset account" button instead?

Psychokiller1888 commented 4 years ago

Yeah, a reset account would be nice :) I do not want to create a new account, i'd have 50 acounts already by now :)

pocketjoso commented 4 years ago

I see. Do you have a lot of resources on your account that are or have been available through the app store? As I think you know, these cannot be deleted, and would remain on your account even after a reset. Knowing this, would the reset still be useful? (i.e. are most of your account resources ones that have never been available through the store)

Psychokiller1888 commented 4 years ago

None are available through the store, they are all auto generated by Alice on Github sync. And as I'm testing and testing and testing new and newer use cases, functions and all throughout the day, we end up with 500+ slots, 50+ assistants, 300+ apps, 100+ intents etc etc etc. When I say we, i mean those that dev on ProjectAlice and all of our testers on alpha

pocketjoso commented 4 years ago

I see, so you have your source code outside, that's why it's no issue for you to empty the account completely, is that correct? It's a bit of an edge case, but if it's difficult for you to clear the account programmatically (not sure we offer endpoint support for this) then we can look into a "Reset account (resources)" button.

For this - a Reset account button - can you please open a new issue? In there, please describe what you would need to be deleted, and also if there's anything that you need to be able to keep in such a reset.

Since it sounds like this is a better fit for your use case, let's continue the discussion in there instead then.