[Suggestion]: Confusing example in UseTransition
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react
- Domain
- documentation
Research direction
Open the linked useTransition documentation example, “Perform non-blocking updates with Actions,” and review how the quantity input and total are presented. Compare the proposed Item example with the current flow, then update the quantity-and-total example so the transition’s purpose is clear around the server call. Done means the revised example is understandable and accurately demonstrates the intended transition behavior.
Written by the indexing model from the issue text.
Description
Summary
In UseTransition example, you have used input as DOM control so it's instantly updating quantity, which is confusing as it suppose to wait for server call then we can understand the use of transition there, I don't find this document is useful, all examples are very confusing.
below code would be helpful. Didn't expect this from react doc itself, I feel I have better understanding than who written this doc's.
export default function Item({quantity, onUpdateQuantity}) { function handleChange(event) { onUpdateQuantity(event.target.value); } return ( <div className="item"> <span>Eras Tour Tickets</span> <label htmlFor="name">Quantity: </label> <input type="number" value={quantity} onChange={handleChange} /> </div> ) }
Page
No response
Details
Please update Use Transition example that is related to quantity and total.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 16h 6m
- Merged PRs (30d)
- 7
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.
More from reactjs/react.dev
-
type: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug: unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
type: typos
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
bug: unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in reactjs/react.dev
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·