More clarification on updating Objects in state
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
here in the current beta docs of updating objects in react, we are just told to treat objects as read only and never try to mutate them but what are the exact tradeoffs if we try to mutate the existing state Object, i am quite confused and may be this requires a brief explanation
Like i have a sandbox below where it tries to just mutate the object directly and it works as expected
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 beta documentation page, updating objects in state, and review the linked CodeSandbox example showing direct mutation. Clarify the exact tradeoffs of mutating an existing state object versus treating it as read-only, so the page explains why the recommended approach matters while addressing the example that appears to work.
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