maproulette / maproulette/maproulette-frontend
Allow users to hide challenges
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem? Please describe.
Trying to view area for challenges results in being flooded by challenges of no interest and no way to hide it.
For example https://maproulette.org/browse/challenges?challengeSearch=19.9258303642273%2C50.052413263334984%2C19.95552778244019%2C50.06358566357687&location=intersectingMapBounds has https://maproulette.org/browse/challenges/37282 which is no really bad - in theory you can try to check online presence of museums.
But for me it is of zero interest, I strictly prefer to solve this by answering StreetComplete quests with less web page crawling and more walking, and with higher success rate.
And bunch of "add localisation" challenges that I cannot process at all as I do not speak Turkish for example.
This crowds out any potentially interesting things that I would want to see.
Describe the solution you'd like
Ability to do exact opposite of favorite: to hide challenge from various listings.
Describe alternatives you've considered
Do not try to use places listing challenges.
Additional context
Maybe, maybe it could be one of indicators to find preferred challenges to show to people (prefer ones with favorites, without ignores)
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 challenge listings and the existing favorite control in the frontend. Trace how challenge visibility and listing filters are handled, then define the hide action and verify that hidden challenges no longer appear in the relevant listings while favorites continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100