codesandbox / codesandbox/codesandbox-client
Confirmation while deleting a CodeSandbox
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
It'd make sense to have a confirmation if the user really wants to delete a CodeSandbox, which is a common UX technique while performing DELETE actions.
It's missing, and yes, there's "Recently deleted" folder.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the CodeSandbox deletion action in the client UI; the issue names no file, test, or entry point. Confirm how deletion currently proceeds and add a confirmation before the DELETE action. Done means users must explicitly confirm before a CodeSandbox is deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100