maproulette / maproulette/maproulette-frontend
Consider hiding flagged challenges where report is not yet processed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 11
Description
I understand that processing flagged challenge takes time (though not really sure how such processing works exactly, see https://github.com/maproulette/challenge-reports/issues/7 from Feb 26)
But maybe hiding flagged challenges from list shown to users on MR homepage would make sense? To reduce exposure of users to problematic ones?
(there is obviously risk of someone maliciously flagging stuff - but if someone is vandal then detecting them and blocking on such easy to revert vandalism would be actually benefit, and it is not feasible to flag so many tasks that MR will run out of things to display)
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 files, tests, or entry points are named. Start by tracing how the homepage loads and displays challenges, then determine how flagged challenges and report-processing state are represented; done would require an agreed behavior for hiding or showing unprocessed reports and validation that the homepage follows it.
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
- Needs clarification
- Newbie friendliness
- 30/100