Progressive Hint Feature
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
- Quiet
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
Research direction
No files, tests, or entry points are named. Start by locating the exercise help and solution UI in the VS Code extension, then trace how exercise state and section limits are handled. Done means a progressive hint flow appears only after testing and iteration, supports three hints, and enforces the proposed solution limits.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
I am an 8th grade student who is completing this course, and a constant problem that i have had is not knowing how to approach a specific exercise. I have seen the help button, but that does not help me understand in any way so i have though of an approach for this problem.
Describe the solution you'd like
My idea is to have a progressive hint button for each exercise. How this would work is it would be disabled before the user starts the exercise and after they have effectively tested and iterated the code the hint button would appear. When it is pressed , there will be a hint that gives them a way to approach the exercise so they do not skip beneficial exercises and cheat on them. The hint button will be able to reactivate 3 times with the same conditions and then there would be a show solution button. that button on the other hand would only be able to be used 3 times a section per part. This way they prevent cheating on all exercises and help the students
Describe alternatives you've considered
I have not had any alternative ideas at this point
Additional context
I have thought about how students could cheat but the restrictions would not allow them to, and even if they do it is to their loss, as they are not learning anything.. The learning students also have a oppurtunity to learn and have help
- Dominant language
- TypeScript
- Stars
- 32
- Forks
- 8
- Avg merge
- 19m
- Merged PRs (30d)
- 2
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 rage/tmc-vscode
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
rage/tmc-vscode#784 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rage/tmc-vscode#783 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
rage/tmc-vscode#779 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rage/tmc-vscode#777 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rage/tmc-vscode#776 · 1 comment ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#33947 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paperclipai/paperclip#20942 ·
Maintainers usually reply within 1 day
-
area: documentation good first issue package: rule-data status: accepting prs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mastra-ai/mastra#30109 · 2 comments ·
Maintainers usually reply within 1 day