RunestoneInteractive / RunestoneInteractive/rs
Multiple attempts at a Parson problem
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 117
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 24
Description
I've created a Parsons problem in PreText syntax, which uses the dag-grader to allow for two possible orderings of early steps. Once done correctly, it is possible to make the second ordering, but trying to check it results in a "no go" icon whn hovering on "Check".
While messing about, we laso got to a state where the green "Check" becam white on click, but no results about correctness were displayed. This happened repeatedly. I can repeat that, but can't say what the steps are, perhaps after a "Reset".
I could demo on Monday, since I know this is brief.
Reading Question 4: Additive closure argument
https://runestone.academy/ns/books/published/proteus_fcla_spring25/section-S.html#reading-S-4-v1
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
Start by reproducing Reading Question 4: Additive closure argument from the linked Proteus page, using the Parsons problem in PreText syntax and its dag-grader. Investigate the second valid ordering and the Reset/Check sequence; done means both orderings consistently produce a visible correctness result instead of a no-go icon or blank Check state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100