Examine usage of getDerivedStateFromProps and refactor if needed
Open
Nobody has claimed this yet.
chore
- Dominant language
- JavaScript
- Stars
- 92
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Related to this comment on #75.
As described in the blog titled 'You Probably Don't Need Derived State', the usage of getDerivedStateFromProps is prone to anti-patterns. We should examine if we made those mistakes (most likely we did) and correct them if needed.
Note: This might involve some considerable overhaul of some of the components in the country page.
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.
Assessment
This issue has not been assessed yet.