Let candidates pick a random problem from a saved practice list
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the lobby, problem cards, and existing recommendation and random-selection logic, then read the tests around those flows. Trace how the lobby stores browser-local preferences and how manual selection and difficulty filters are maintained. Done means candidates can persist a marked problem list, draw only from it with the stated repeat-selection behavior, and pass tests for persistence, add/remove, and selection.
Written by the indexing model from the issue text.
Description
Who is affected
Candidates who want to practice a hand-picked subset of problems without choosing each next problem manually.
Current behavior
The lobby can recommend or randomly select a problem from the available problem bank, but candidates cannot create a personal list and draw only from that list.
Desired outcome
Let candidates mark problems for a personal practice list, then request a random problem from the marked problems.
Scope
- Add a separate control on each problem card to add or remove that problem from the practice list.
- Save the selected problem IDs in the current browser.
- Add a “Pick from my list” action that selects uniformly from marked problems, regardless of the difficulty filters used for general recommendations.
- Keep the existing recommendation and random-selection behavior unchanged.
- Do not sync the list across accounts or devices.
Acceptance criteria
- Candidates can add and remove problems from their practice list.
- The list remains available after reloading the lobby in the same browser.
- “Pick from my list” chooses only a marked problem.
- When more than one problem is marked, repeated draws avoid immediately selecting the current problem when another marked problem is available.
- The action is disabled with a clear explanation when the list is empty.
- The feature works with the existing difficulty filters and manual problem selection without silently changing either preference.
- Automated tests cover list persistence, add/remove behavior, and random selection from only the marked problems.
Related: #210 changed how the existing random selection handles difficulty and review priority. This proposal adds a user-curated pool as a separate selection mode.
- Dominant language
- Rust
- Stars
- 177
- Forks
- 100
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 135
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from sysprog21/codetrial
-
Audio output can be confirmed without playing a test soundPossibly taken @ChenYingHan1121 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
sysprog21/codetrial#359 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Add a Copy code button to the final reportPossibly taken @yansawu claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
sysprog21/codetrial#318 · 5 comments · 2 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
C tests accept a wrong next pointer on the last node in Org Chart Row NavigationPossibly taken @winter77777 claimed this 1 day ago. Open
sysprog21/codetrial#370 · 1 assignee ·
Maintainers usually reply within 1 day
-
"Let me think about it for a moment" does not start a thinking holdPossibly taken @PeteChiang1211 claimed this 1 day ago. Open
sysprog21/codetrial#369 · 1 assignee ·
Maintainers usually reply within 1 day
-
Switching programming languages clears editor undo historyPossibly taken @Chingyong0905 claimed this 1 day ago. Open
sysprog21/codetrial#365 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in sysprog21/codetrial
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 8 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
swc-project/swc#12576 ·
Maintainers usually reply within 1 day
-
good first issue gpu serve
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day