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

Tracker: reduction dropdown logic

Open
  • Is something wrong?
#292 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

This is an umbrella tracker; no implementation files or tests are named. First read the ReduxISU/Redux classification work, which this issue says blocks the directionality rule, then inspect the existing reduction filter associated with #19 and #46. Done means applying #46's direction rule with corrected classification data and checking whether #19's remaining filter symptoms are resolved.

Written by the indexing model from the issue text.

Description

tracker

Summary

Two issues describing one broken filter: which problems are offered as reduction targets for the currently selected problem.

Why these are grouped

#19 reports the general breakage — the list sometimes includes problems that should not be there, sometimes omits correct ones, and sometimes fails to highlight the right entry (Knapsack shows no reductions at all despite Partition existing). #46 is a specific, well-defined rule that the same filter is missing: reductions are directional, so an NP-complete problem should not appear as a reduction target for a P problem (3SAT reduces to Deutsch's, not the reverse).

They are one fix to one filter. #46 is essentially the rule that, applied correctly, resolves a good share of #19's symptoms.

Blocked on: ReduxISU/Redux — the direction rule needs correct complexity-class data per problem, which is what the classification tracker there is settling. Implementing #46 against today's misfiled quantum problems would produce wrong answers.

Suggested order

  1. wait on correct classification data from ReduxISU/Redux
  2. #46 — implement the directionality rule
  3. #19 — verify the remaining symptoms against the corrected filter

Related (not re-parented)

Opened by other contributors, so linked for context only — their state is unchanged:

  • #19 — Problem Reduction Logic (@Andrija-Sevaljevic)
  • #46 — P-problems should not have NP-complete problems show up as possible reductions to be added (@norkish)

[!NOTE]
No sub-issues attached: these were opened by @Andrija-Sevaljevic and @norkish, so they are cross-linked for context only and their state is unchanged.

Issue Handling

Umbrella/tracker issue grouping existing work; no new scope is introduced here. Nothing is closed by this issue directly.

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.