Explain when to avoid React memo hooks
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
I feel there is a lack of explanation of when to use, and when not to use some React hooks.
I know useMemo and useCallback are for memoization, but it does not explain the good and bad things about it.
- When will they go against me and make my code more slow?
- Could I wrap all my local functions in useCallback? Why? Why not? Which ones?
- Could I wrap all my local variables in useMemo? Why? Why not?
Thanks!
Contributor guide
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 existing documentation page is named. Start by locating the React documentation covering useMemo and useCallback, then review how their current guidance addresses memoization. Done means adding clear guidance on when these hooks help, when they add cost, and which functions or values should not be wrapped automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100