Offer non-spoiling area hints
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- accessibility, frontend, game-dev
Research direction
No file paths are named. Start by locating the puzzle interaction and state entry points, then read the existing rule and component tests and the untimed submit-and-reveal result flow. Done means focused tests and human checks cover deterministic, non-spoiling hints for nested and overlapping puzzles across pointer, touch, and keyboard input.
Written by the indexing model from the issue text.
Description
Goal
Offer an optional hint that narrows the search area without drawing or identifying an unfound rectangle.
Background
A hint should preserve observation and agency. It may indicate a region containing at least one missed rectangle, but must not expose the rectangle itself or the hidden total.
Acceptance criteria
- Hints are player-initiated and never interrupt ordinary play.
- A hint indicates an area containing an unfound rectangle without outlining that rectangle.
- Hint state is understandable without relying on colour alone.
- Repeated hints have an explicit, non-revealing rule.
- Hint use is represented in the submitted result without shaming language.
- Pointer, touch, and keyboard users receive equivalent hints.
- The feature remains local-first and deterministic.
Verification
- Add focused rule and component tests.
- Exercise hints on nested and overlapping puzzles with pointer and keyboard.
- Conduct a human check that hints help without solving the puzzle.
Dependencies
- The untimed submit-and-reveal journey and curated puzzle library.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 5m
- Merged PRs (30d)
- 14
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.
More from glowkeeper/rectangle-react
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 48/100
All issues in glowkeeper/rectangle-react
Similar issues
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DavidAnson/markdownlint-cli2#940 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100