Add LeetCode problem numbers to UI problem mappings
Maintainers usually reply within 1 day
Assessment
This issue has not been assessed yet.
Description
Description
Currently, the problem cards in the web interface display the mapped LeetCode problem name without its corresponding problem number (e.g., displaying "LeetCode: Valid Parentheses" instead of "LeetCode: 20. Valid Parentheses").
Because LeetCode problems are frequently referenced, discussed, and searched by their official numbers, this omission makes it difficult for users to quickly cross-reference problems or verify their selections.
Adding the problem number to the display text will significantly improve discoverability and provide clearer immediate context for users navigating the problem picker.
Expected behavior
When a problem card or selected problem status is rendered in the UI, the official LeetCode problem number should be prepended to the problem title.
The display format should be updated to "LeetCode: {number}. {Title}" (e.g., "LeetCode: 191. Number of 1 Bits").
This format change should apply consistently across the problem picker cards and any other relevant UI elements showing the problem mapping.
Acceptance criteria
- The LeetCode problem numbers are added to the problem bank and flow through
scripts/gen-problem-cards.pyinto the generated frontend files. - The format string consistently matches "LeetCode: {number}. {Title}" (e.g., "LeetCode: 191. Number of 1 Bits").
- The problem numbers and sources are only visible when the "Show sources" toggle is active, preserving the existing toggle behavior.
- The format change applies consistently across the problem picker cards and the completed interview reports/history (aligning with the implementation in #152 and PR #334).
- The layout of the problem cards remains stable and responsive when accommodating the slightly longer text.
- Existing features (problem selection, difficulty filters, random problem selection) remain completely unaffected.
- Browser regression coverage or relevant frontend tests are updated to verify the new text format, toggle behavior, and ensure no layout breakage.
- Dominant language
- Rust
- Stars
- 215
- Forks
- 141
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 220
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 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
sysprog21/codetrial#359 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Web lobby cannot reopen Setup after configurationPossibly taken @YEH-YU-YANG claimed this today. Open
sysprog21/codetrial#525 · 1 assignee ·
Maintainers usually reply within 1 day
-
Offer a way back to Setup from the lobbyPossibly taken @Patriciaath999 claimed this 1 day ago. Open
sysprog21/codetrial#513 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Jim's stage covers the editor, and Hide avatar does not free the spacePossibly taken @Phonlin claimed this 1 day ago. Open
sysprog21/codetrial#512 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Collapse the specific-problem picker after choosing a specific problemPossibly taken @8woodyc claimed this 1 day ago. Open
sysprog21/codetrial#505 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in sysprog21/codetrial
Similar issues
-
component:benchmark
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agentic-os-org/ANOLISA#9177 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oracle/rust-oracledb#61 ·
-
bug priority-medium to-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Databricks tool-only response crashes in resolve_reasoning_and_content with KeyError: contentPossibly taken @1divyanshdev claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
BerriAI/litellm#48637 · 2 comments ·
Maintainers usually reply within 1 day