Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Picking "Grover's Algorithm" on Unstructured Search is ignored: the solver name maps to SAT's Grover solver

Open Beginner friendly
  • Is something wrong?
#405 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, redux
Domain
frontend

Research direction

Start in SearchBarExtensible.js and trace how onChange maps the selected label using getKeyByValue and how the current problem’s solver list is provided. Reproduce the duplicate "Grover's Algorithm" labels for SAT and Unstructured Search, then constrain the lookup to that problem or use class names as option values. Done means selecting Grover’s Algorithm on Unstructured Search activates its Grover solver instead of leaving brute force selected.

Written by the indexing model from the issue text.

Description

In SearchBarExtensible.js, onChange maps the chosen label back to a class with getKeyByValue(optionsMap, label). The solver name map covers every problem, and both SATGroverSolver and Unstructured Search's Grover solver are named "Grover's Algorithm". So choosing it on Unstructured Search resolves to SATGroverSolver, which isn't in that problem's list, and the choice is silently ignored: the input shows "Grover's Algorithm" but the page keeps solving with the brute-force solver.

Fix idea: map labels to classes only within the current problem's solver list (or keep the class name as the option value), so equal display names on different problems can't collide.

Found while checking Redux#625 (quantum solver failures) in Redux_GUI, Oct 22.

Dominant language
JavaScript
Stars
3
Forks
18
Avg merge
22h 57m
Merged PRs (30d)
37

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 ReduxISU/Redux_GUI

All issues in ReduxISU/Redux_GUI

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.