Suggestion to clarify the usage of ref / useRef for storing data
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
According to this question and confusion between docs pages, is it possible to make thing more clear on the first docs link?
fewer restrictions for ref usage, not only for DOM elements.
maybe add a "note" or something
what do you say?
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 refs-and-the-dom documentation page and compare it with the linked Stack Overflow question about useRef for one-time initialized data. Clarify whether refs may store non-DOM data and make the guidance consistent with the related docs; done when the page addresses the reported confusion without implying refs are only for DOM elements.
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
- 45/100