Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
[Gantt Chart] - 1.4.4 Memoization
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
Add memoization to project-level components.
Components re-render when their parent re-renders and passes new prop references, even if the actual values are identical. This commonly happens when a parent passes an inline function or object. JavaScript creates a new function/object on every render, so React sees "a new prop" and re-renders the child, even though nothing meaningful changed. React.memo (wrapping a component so it skips re-rendering if props are shallow-equal), useMemo (memoizing an object/value), and useCallback (memoizing a function) fix this.
Acceptance Criteria
TBD
Proposed Solution
TBD
Mocks
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files or tests; start by locating the project-level React components in the FinishLine repository and inspecting where their parents pass functions or objects. Confirm which components are in scope, then define acceptance criteria that show unnecessary re-renders are avoided and run the relevant existing frontend checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100