klesh commented on issue #8418: URL: https://github.com/apache/incubator-devlake/issues/8418#issuecomment-2874800878
> Hi [@klesh](https://github.com/klesh) > > Yes I'm working on it, going through code and structure, i have below 2 designs in mind. > > 1. One way: They pick the connections they want gone, then hit a "delete" button. A little window pops up showing how each one is doing as it gets deleted. > Thing I'm wondering about: If one of them fails to delete, should I just ignore it and keep going? Also, if something else is happening (like a pipeline running), we can't let them delete anything. What's the best way to tell them that? "should I just ignore it and keep going?" - How about offering a checkbox for people to choose what they prefer. " if something else is happening (like a pipeline running), we can't let them delete anything. What's the best way to tell them that?" I think an error message about what happened and asking them to try again later is necessary and sufficient. > 2. Another way: The user picks the connections, and then we tell the system to delete them all in one go. > Thing I'm wondering about here: If deleting a lot of connections takes a while, the system might time out. How do we stop that from happening? Also, if some of the chosen connections don't get deleted, how do we let the user know which ones? Good points, too many to consider. I think the first way is better, plus, it can be implemented purely in the frontend interactively. > > can you please provide your input which and how to go about it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
