Don't recommend getDerivedStateFromProps as explicitly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html still contains a few recommendations to use getDerivedStateFromProps like:
As of version 16.3, the recommended way to update state in response to props changes is with the new static getDerivedStateFromProps lifecycle
We should figure out a way to dial them down or at least direct people to the newer blog post.
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
Start with the linked 2018 async rendering blog post and review each recommendation to use getDerivedStateFromProps. Compare the guidance with the newer blog post referenced in the issue; the work is done when the recommendations are softened or direct readers to the newer guidance.
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
- 35/100