You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice that the trash can button at the dataset row, on hover will expand and show text "Delete" in addition to the icon (please reach out to Harley if the mock doesn't reflect this hover behavior)
On trash can / delete button click, we show a confirmation modal as a checkpoint
Once user decides again to delete, we send a POST call to backend. If we get success response, we refetch all datasets, and the pending delete dataset should no longer be displayed
Please note that since cancel also hits the same DELETE endpoint, we'll also implement the cancel flow in this ticket!
The text was updated successfully, but these errors were encountered:
tihuan
changed the title
Dropbox Integration for Upload Dataset Part 4 [Delete Dataset]
Dropbox Integration for Upload Dataset Part 4 [Delete/Cancel Dataset]
Nov 10, 2020
brianraymor
changed the title
Dropbox Integration for Upload Dataset Part 4 [Delete/Cancel Dataset]
Upload Dataset Part 4 [Delete Dataset/Cancel Upload]
Nov 10, 2020
Refinement note from @tihuan - 706 (Delete / Cancel Dataset) has a slight coupling with 705, because of the conversion cancellation trash can. But I think all three tickets can still be done in parallel, and I can create an integration ticket between 705 and 706 for 1 point, if we end up parallelizing 705 and 706!
Design: https://www.figma.com/file/g0L0CfVzRc8r6HQa4NH1wJ/Publisher-Collection?node-id=493%3A225
What:
After finishing this PART 4 ticket, the user will be able to delete/cancel a dataset
Delete Dataset
No need to do delete collection
Render the dataset entry as a row, as shown in design here -- Please double check with @hthomas-czi this is the correct design 🙏
API doc is here - to delete a dataset, call the
DELETE
endpointBE tickets here
User Flows:
Notice that the trash can button at the dataset row, on hover will expand and show text "Delete" in addition to the icon (please reach out to Harley if the mock doesn't reflect this hover behavior)
On trash can / delete button click, we show a confirmation modal as a checkpoint
Once user decides again to delete, we send a POST call to backend. If we get success response, we refetch all datasets, and the pending delete dataset should no longer be displayed
Please note that since cancel also hits the same
DELETE
endpoint, we'll also implement the cancel flow in this ticket!The text was updated successfully, but these errors were encountered: