A problems fence: math problems reader can check

Open
#125 0 comments 0 reactions 0 assignees View on GitHub

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

enhancement

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 = ? accepts 1/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: maybe 3 + 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 with math:[…].
  • 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jzheaux/reader

All issues in jzheaux/reader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.