iiitl / iiitl/Event_Dapp

[Medium]: Refactor legacy commented code and reduce component complexity

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

Nobody has claimed this yet.

difficulty:medium frontend help wanted
Dominant language
JavaScript
Stars
0
Forks
9
PR merge metrics
No merged PRs in 30d

Description

### Problem Statement

Refactor legacy commented code and reduce component complexity

### Proposed Approach

Remove obsolete large commented blocks.
Keep only active code paths.
Group active logic into cleaner sections.
Extract repeated helper logic where needed.
Keep behavior and UI unchanged.
Validate major user flows after cleanup.

### Files and Scope

event-dappp/src/App.js
event-dappp/src/components/EventList.jsx
event-dappp/src/components/CreateEventPage.jsx
event-dappp/src/components/UserProfile.jsx

### Acceptance Criteria

- [ ] Large obsolete commented blocks are removed
- [ ] Active code structure is easier to read
- [ ] Repeated helper logic is extracted where useful
- [ ] No user-facing behavior regression is introduced

### Test Plan

Run frontend app and test event list, create event, and profile pages.
Run frontend tests and confirm no breakage.
Compare behavior before and after cleanup.

### Risks and Edge Cases

Accidentally deleting still-needed logic.
Refactor may break prop flow if not verified carefully.

Contributor guide

Open the 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.

Research direction

Start by reading event-dappp/src/App.js and the three listed component files, identifying commented blocks and repeated logic while tracing their active prop flow. Run the frontend tests and manually check the event list, create-event, and profile pages before and after the cleanup. Done means the obsolete comments are removed, active code is easier to follow, and behavior and UI remain unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.