If I accidentally click on New Query or only want to try something there would be useful to delete the draft. About half of my queries could be deleted (I marked them with ~ tilde in name). There should be a possibility to delete a draft.
Description
Related Objects
Event Timeline
Hi, mw:Talk:Quarry is the place to ask Quarry questions or for Quarry help. Phabricator is mostly for feature requests or bug reports.
I think this is a fair enough request, since there's no way to actually do this right now in Quarry
I'm not sure we should delete anything (short of doxing and the like). Maybe we can "archive" a draft so that it doesn't appear in your history of queries unless a "show archived queries" box is checked.
That's not so different from my current solution of renaming the unused queries to "~" and use them as a clean paper for new queries in the future.
I understand not deleting already published queries, but (in my opinion) drafts could be deleted without loosing any important content.
(I also do not fully understand publishing queries, if my not published drafts can see anybody logged in.)
Indeed, everything is public, and I think we're careful to not call them 'drafts' (if not we should be!)- published just means you are finished tweaking them for a bit.
Not sure what the right thing to do here is.
What I do — I just reuse the queries which better'd be deleted or which were just those empty ones. Once you've renamed and changed it nobody knows what it was before that. Perhaps some process for marking queries for reuse could be added (like a separate section where you can move queries to and from so that you can keep queries to be reused in there together, or any other way)
@Base The same as I do. That is a great idea to add a possibility to mark them for reuse.
btw: Maybe better would be draft vs done (instead of draft vs published) if everything is public
The drafts can already be renamed, and their description and query can already be overwritten and resubmitted to effectively blank them permanently. As such, the ability to delete a draft wouldn't lose anything users can't already remove by hand, except for the url to return 404 instead of an empty draft.
But who wants to have a list full of empty drafts (like me)
BTW I use empty/emptied drafts to make "folders" (T164825: Add some type of folders/categories/sorting to user page)
Right. I think it makes a lot of sense to *archive* old queries so that they don't clutter up useful, but not-worth-publishing queries. Given that queries don't take up a huge amount of drive space, it seems the only reason for deleting them is to de-clutter one's activity history.
Any solution to these two problems (possibility to hide unused and possibility to reorganize used in some fashion) would be great