Why you did not mention the name of empty wrapper?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Link
https://beta.reactjs.org/learn#writing-markup-with-jsx
In this paragraph you wrote :
JSX is stricter than HTML. You have to close tags like <br />. Your component also can’t return multiple JSX tags. You have to wrap them into a shared parent, like a <div>...</div> or an empty <>...</> wrapper:
I"d recommend to add the name of the empty Wrapper Fragment and provide the two version of it:
function AboutPage() {
return (
<Fragment>
<h1>About</h1>
<p>Hello there.<br />How do you do?</p>
</Fragment>
);
}
The shortcut:
function AboutPage() {
return (
<>
<h1>About</h1>
<p>Hello there.<br />How do you do?</p>
</>
);
}
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 the linked React Learn page and locate the paragraph beginning “JSX is stricter than HTML.” Update it to name Fragment and show both the explicit Fragment syntax and the empty-tag shortcut. Done means the page clearly presents both forms alongside the existing wrapper explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100