Need ease of use bounty tracking/ignoring
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 1.5k
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
Currently all the bounties are shown in a filtered by language list. With the amount of bounties there, this is kind of hard navigate around. On top of that, some bounties are internal, or just isn't filtered by language at all. So, I propose having lists of favorite bounties, remaining bounties and ignored bounties. I believe having a distinct ignore list on top of favorite list is important because it allow someone to unignore it if they change their mind, but most importantly it also reduces the clutter on the list of new bounties and allows people to see the new bounties more easily.
This can be done on client-side with client-side storage; I think that solves this for majority of the use cases without the headache of keeping extra data for users on the server. Though a second look at it, as it uses phoenix liveview, I don't know how weird this would be.
Contributor guide
No contributing guide indexed for this repository
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 or tests are named. Start by tracing the Phoenix LiveView bounty list and its language filtering, then determine how favorites, remaining bounties, and ignored bounties should behave, including whether client-side storage is suitable. Done means the lists reduce clutter and allow ignored bounties to be restored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100