reactjs / reactjs/react.dev

Document memoization as alternative to componentWillReceiveProps

Open
#830 1 comment 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: documentation
Dominant language
JavaScript
Stars
11.8k
Forks
7.9k
Avg merge
1d 11h
Merged PRs (30d)
11

Description

We get a lot of feedback that getDerivedStateFromProps is used for memoization which is not very ergonomic.

Let’s add a recipe about memoizing directly to the docs.

https://twitter.com/brian_d_vaughn/status/987443099537309696?s=20

We should probably use this package:

https://www.npmjs.com/package/memoize-one

It’s important to highlight that we usually recommend memoizing just the last value.

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 reviewing the existing React documentation recipes and the proposed memoize-one package. Add a documentation recipe explaining memoization as an alternative to componentWillReceiveProps and getDerivedStateFromProps, with emphasis on memoizing only the last value.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.