maproulette / maproulette/maproulette-backend
Better use of the overview map
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
If the Challenge is quite large, some people prefer to work on their local area. A simple solution is for them to use the Challenge overview map. Two problems:
- you can't currently open a single Task in a new tab, so you need to reload the map every time you do a Task
- objects that have already been reviewed do not disappear from the map. It would be nice if they had a different icon or disappeared all together
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
No source files or tests are named. Start by locating the Challenge overview map entry point and the code serving task links and reviewed-object state; confirm how opening a task and review status are represented. Done means tasks can open in a separate tab and reviewed objects have a distinct icon or no longer appear on the map.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100