A problems fence: math problems reader can check
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by reading the repository’s existing puzzle and graph fence implementations, since the issue says problems should follow the puzzle model and share an exact expression parser with the graph fence. Then identify how fence text and student progress are stored. Done means playable problems have exactly one exactly computed answer, while unsupported or ambiguous problems remain non-playable; the issue leaves answer display, checking, and layout decisions open.
Written by the indexing model from the issue text.
Description
Idea
Teachers make packets of exercises. A problems fence holds math problems, one per line, with ? where the answer goes. Reader works out each answer itself, so the student's answers can be checked and an answer key drawn (#13) without anyone writing the answers down.
3 + 5 = ?
? + 5 = 8
12 ÷ ? = 4
1/3 + 1/6 = ?
3/4 ? 2/3
As with the puzzles, the fence's text is the problems and the progress made on them: each answer is written back into the file.
The rule
Every problem must have exactly one answer that reader can work out. That covers:
- Arithmetic with
?anywhere: one unknown in a linear equation, which is cheap to solve exactly. - Fractions and order of operations, using exact numbers (whole numbers and fractions, no floating point), so
1/3 + 1/6 = ?accepts1/2. - Comparisons:
3/4 ? 2/3, answered with<,>or=.
A problem reader can't solve, or that has more than one answer, is shown as a problem (in the problems panel once #16 is there), not drawn as playable.
Out of scope: "simplify", "factor" or "show your work". Those have more than one acceptable written form and would need a full algebra system.
An expression parser, shared
This needs a small parser that evaluates expressions exactly. The graph fence needs the same one to evaluate y = 2x + 3, so build it once for both.
Questions
- Where do the answers go in the fence? Inline after the
=(3 + 5 = 8) reads naturally, but the?has to stay findable: maybe3 + 5 = [8]. - Does the student see right or wrong as they go? A teacher may want
check: off, so it only shows on the key. - Layout: a column per problem for the youngest (stacked addition, carrying), or a row.
::: grid(#44) can lay several fences, or a fence's problems, out in columns. - Name: not
```math, which GitHub renders as LaTeX, and which would clash withmath:[…]. - Word problems: prose, then
= ?with a unit?
Generating problems ("20 sums under 10") belongs in the worksheet author, in reader-authors, not in reader, so the file stays the record of exactly what the student got.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 26
Getting set up
- Ships a 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 jzheaux/reader
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
polish
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
accessibility good first issue languages
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 2 days
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100