maproulette / maproulette/maproulette-frontend
In Quick Fixes, when no tag changes are proposed, offer appropriate action
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 11
Description
When loading a quick fix task, it is possible that the tag changes were already resolved outside MapRoulette, resulting in a confusing situation for the mapper.
A few possiblities:
- quietly skip the task, marking it as 'automatically fixed'
- offer the mapper an explanation: "this task was already fixed outside MapRoulette [CONTINUE]
or something else?
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 in the Quick Fixes task-loading flow and reproduce the case where no tag changes are proposed. Review the available outcomes in the issue, then determine and implement the agreed mapper-facing action, including the wording shown to the mapper. Done means the no-change case is no longer confusing and follows the selected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100