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

Search Tree renderer

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

Maintainers usually reply within 1 day

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, redux
Domain
frontend

Research direction

Read the Search Tree tab mockup at Documentation/Visualizations/mockups/searchtree.js and review the existing step format and dependencies in ReduxISU/Redux#719 and #352. The renderer is intended to show solver decisions, tried branches, cut or backed-out branches, and the answer path using parentId and an optional bound; done means it works as a second view for the listed problem solvers once they record steps.

Written by the indexing model from the issue text.

Description

enhancement

Part of #353. (Moved from #369: Search Tree is now one of the built picture types.) The solver's choices as a growing tree: each node a decision, branches tried, cut (with the bound or clash that cut them) or backed out of, the answer's path. A step is the existing step plus a parentId (and an optional bound). Built in the backend by ReduxISU/Redux#771 as a second view for 3SAT, TSP, Graph Coloring, 3-Dimensional Matching and N-Queens (their backtracking and branch-and-bound solvers).

Spec: design mockup tab "Search Tree"; reference Documentation/Visualizations/mockups/searchtree.js in Redux. Depends on: ReduxISU/Redux#771 (replaces #719, closed), #352.

Dominant language
JavaScript
Stars
3
Forks
18
Avg merge
1d 3h
Merged PRs (30d)
35

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.