manishkumar8312 / manishkumar8312/QuickStay
Static Filter Data Not Optimized with useMemo – Potential Performance Concern
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
While reviewing the code, I noticed that static arrays like roomTypes, priceRange, and sortOptions are being redefined on every render within the component. This isn't ideal, as it can lead to unnecessary re-renders and memory usage.
If u assign this i will start working on this
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
No file or test is named. Locate the frontend component defining roomTypes, priceRange, and sortOptions, then inspect how those arrays are used by the filters and whether their identity affects downstream renders. Done means the static data is not recreated on each render while filtering behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend, performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100