Consider hiding flagged challenges where report is not yet processed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
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.
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)
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 11
Getting set up
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.
More from maproulette/maproulette-frontend
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
maproulette/maproulette-frontend#2923 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
maproulette/maproulette-frontend#2922 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
maproulette/maproulette-frontend#2909 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
maproulette/maproulette-frontend#2900 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
maproulette/maproulette-frontend#2896 · 4 comments ·
Maintainers usually reply within 1 day
All issues in maproulette/maproulette-frontend
Similar issues
-
Complexity: Small P-Feature: Projects page ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
bellingcat/toolkit#905 ·
-
self-care self-care:docs-build-time-investigator
Difficulty 2/5 Half a day Newbie friendliness 76/100
githubnext/gh-aw-cao#14191 ·
Maintainers usually reply within 1 day
-
effort:low impact:medium RAG status: auto-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mastra-ai/mastra#25229 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sugarlabs/musicblocks#8984 ·
Maintainers usually reply within 1 day