-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking Issue for "Crate Deletions" #9352
Comments
Two pieces of feedback now that I've tested the
I forgot what the RFC actually decided on, and I missed that little "or" at the end of the first requirement. It would be nice if that was a bit more obvious, either put a big "OR" between 1 and 2 along the left, or maybe change "A crate can only be deleted if" to something like "A crate can only be deleted if one of the two following applies".
|
thanks for the feedback! I had that thought about the email as well, but somehow forgot about it again... 😅 |
feedback from a support request:
this was from a couple of crates that were created 2 months ago, had a couple of versions and about 1000 downloads |
This is a tracking issue for the RFC "crates.io: Crate Deletions" (rust-lang/rfcs#3660).
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps
DELETE /api/v1/crates/:crate_id
endpoint #9904)/crates/:name/delete
route #10177, Add "Delete this crate" button to the crate settings page #10343)Implement version deletion API endpointImplement version deletion user interfaceUnresolved Questions
The text was updated successfully, but these errors were encountered: