maproulette / maproulette/maproulette-backend
Delete challenge
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
I clicked on the "Delete" button in the challenge and it deleted the challenge without asking again. For a large operation like this, I would expect an "Are you sure?" question.
Strangely the challenge was still there, there was only a small popup showing that I deleted it, but in the list it was still there. When I clicked on the challenge, which normally gives me the task list, I got an error page. The error page showed me as the anonymous user, so I had to go back to the Maproulette main page to get maproulette to know my user again before continuing.
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
The issue names no files, tests, or entry points. Start by reproducing challenge deletion and the subsequent challenge-list and error-page behavior, then trace the relevant backend request flow; done means deletion requires confirmation, the challenge state is consistent, and the user session remains recognized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100