after introducing hooks this phrase is misleading
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
after introducing hooks this part is misleading, as converting into class is no longer the only option, that can be used if state needed for the component
You should convert the component to a class if you need a ref to it, just like you do when you need lifecycle methods or state.
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
Open content/docs/refs-and-the-dom.md and read the “Refs and Function Components” section linked in the issue. Update the quoted guidance so it no longer presents converting to a class as the only option when state is needed, then verify the revised wording in the documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100