maproulette / maproulette/maproulette-backend
Creating a challenge with duplicate name yields 500 error
Open
Nobody has claimed this yet.
BACKLOG
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
We should do this more gracefully (for example checking the name before moving on to the geometry part of the challenge creation process)
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 reproducing challenge creation with a duplicate name and trace the back-end/API flow through the name check and geometry-processing step. Done means duplicate names receive a graceful non-500 response rather than failing with a 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100