[Suggestion]: use toSorted and toReversed for the examples in Updating Array in State Page
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Summary
Update this section Updating arrays without mutation by adding toReversed() and toSorted() instead of suggestion cloning the array and mutating it.
Page
https://react.dev/learn/updating-arrays-in-state
Details
Since toReversed() and toSorted() have been added to Javascript, should the docs reflect the changes and remove the section about mutating the array before sorting and reversing?
Or does it stay just to give an example of cloning before mutating an array ?
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 “Updating arrays without mutation” section on the Updating Arrays in State page and review its sorting and reversing examples. Check how toSorted() and toReversed() should fit the existing explanation, then confirm whether the cloning-before-mutation example should remain; done means the page reflects the decided guidance and its examples are consistent.
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
- 42/100