maproulette / maproulette/maproulette-backend
Better feedback on Overpass query
Open
Nobody has claimed this yet.
admin
BACKLOG
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
It's not clear to the user why an Overpass query fails. Let's discuss what the options are to give better feedback. One idea is to get the error from the Overpass API and feed that back to the user in a little info popup next to 'failed'.
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 locating the Overpass query handling and the UI/API path that reports a query as failed; the issue names no files or tests. Review how Overpass API errors are currently surfaced, then define the feedback approach and acceptance criteria before implementing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100