Bug: React Docs Beta - Keeping Components Pure
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Inside Keeping Components Pure you will find a topic Side Effects: (un)intended consequences, in the first example where it shows component that break this rule , the output produce by given example is not correct it return
Tea cup for guest #1
Tea cup for guest #2
Tea cup for guest #3 not
Tea cup for guest #2
Tea cup for guest #4
Tea cup for guest #6
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 at the React documentation beta page Keeping Components Pure, then open the Side Effects: (un)intended consequences section and inspect its first example. Compare the rendered output with the example code and correct the documented output so it accurately reflects the example; verify the page displays the corrected sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100