refactor: feedback form contains dead/abandoned code

Open Beginner friendly
#478 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
react, typescript
Domain
frontend

Research direction

Start in FeedbackForm.tsx by reviewing the useMutation block, the commented submission and UI sections, and the submit button's isLoading reference. Remove the abandoned code and unused imports, then ensure the button no longer depends on the removed mutation while preserving the existing onSubmit flow. Run the project's frontend checks to confirm the form still works.

Written by the indexing model from the issue text.

Description

Documentation

Current State:

FeedbackForm.tsx contains dead code from an abandoned feature:
An unused useMutation block (lines 81-100) that posts to a non-existent localhost:3001/text_extraction endpoint. The mutation is never triggered — only its isLoading value is used by the submit button.
~50 lines of commented-out image attachment submission logic (lines 127-178)
~70 lines of commented-out image attachment UI (lines 354-421)
The actual form submission is handled by onSubmit (line 112), which works fine independently.

It looks like the image submission feature was abandoned. The commented out code looks irrelevant now, since it included a Jira integration. Just remove it and we can come back to this later if we want to allow image attachments in the feedback form.

Changes needed:

Remove the useMutation block, all commented-out code, and any unused imports (e.g. useMutation from react-query). The submit button (around line 433) references isLoading from the removed mutation.

Dominant language
TypeScript
Stars
21
Forks
19
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 CodeForPhilly/balancer-main

All issues in CodeForPhilly/balancer-main

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.