Closed KonstantinGasser closed 3 years ago
No. Because if a group has large number of account, then one has to delete all accounts one by one. That would be kind of cumbersome, from usability perspective.
I think, if the group has accounts, then confirmation while deleting the group should be enough? I don't think, rollback would involve keeping the deleted data for some time & allowing users to rollback within certain time-period, which involves a bit more complexity, than the benefit one gets it from. Thoughts? May be Rollback is a feature that can be considered in further iterations of the tool, wherein the tool is all-time running as a daemon & then such things will become easier to handle.
@amit-pub thanks for your thoughts on that. For the first point I think we misunderstood: deleting a group with multiple account should work without deleting each account by itself (as mentioned in point 2.). However, if the last account in a group gets deleted should the group then also be automatically be deleted - I think it should not..
Regarding your second point: I agree with you that for now a rollback is not so much required. An idea I had is similar to yours, that a some point it would be cool so have a service running in a local network and accounts could have shared permission and can be retrieved by multiple people in the networking with the right permissions. At this stage thinking about a rollback feature could make sense, yes 😄!
However for this issue I think deleting a group should be the only concern.
something like sherlock del group group-name
deletes a group instantly if no account are mapped to it, else asks for confirmation, what du you think?
IMO the user should be able to delete a group - however there are some things to consider:
groups
be deleted if its lastaccount
has been deleted?group
sounds like a dangerous thing. Should there be a different conformation dialog? a rollback option?