Documentation/blog update suggestion - overloading controlled/uncontrolled
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Hi,
Overall the Documentation is great.
https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html … - overloads the terms controlled/uncontrolled .I can have a controlled component from a form perspective but uncontrolled from a data residence perspective .This can be confusing. I suggest some new terminology to fully differentiate these different concepts.
Regards
John
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 by reading the linked React blog post and review how it uses “controlled” and “uncontrolled.” Determine whether distinct terminology is needed, then identify the affected documentation pages and update the terminology consistently if a clear proposal is accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100