-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #110 from Eli017/patch-1
Create 33.react-fragments.md
- Loading branch information
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# React Fragments | ||
|
||
React fragments are used whenever a component needs returned with multiple children. | ||
|
||
Specifically, fragments are useful when I don't want to clutter the DOM with unnecessary `<div>` tags that are used purely to wrap children in a React render method. | ||
|
||
For example, React fragments are commonly used to render list items: | ||
```javascript | ||
render() { | ||
return ( | ||
<React.Fragment> | ||
<td>Table Cell 1</td> | ||
<td>Table Cell 2</td> | ||
</React.Fragment> | ||
); | ||
} | ||
``` | ||
|
||
This solves the issue of breaking the DOM HTML table specifications by not adding unnecessary `<div>` elements around `<td>` elements. | ||
Do keep in mind, if it is a list being rendered, React does still throw warnings when children don't have the `key={}` prop. | ||
|
||
### Related links: | ||
- https://reactjs.org/docs/fragments.html |