In either case, we still need need a container element surround the inner elements.
My question is, why is using a Fragment
preferable? Does it help with performance? If so, why? Would love some insight.
asked 2 months ago
1Answers
4Views
In React 16.2, improved support for Fragments
has been added. More information can be found on React's blog post here.
We are all familiar with the following code:
render() {
return (
// Extraneous div element :(
<div>
Some text.
<h2>A heading</h2>
More text.
<h2>Another heading</h2>
Even more text.
</div>
);
}
Yes, we need a container div, but it's not that big of a deal.
In React 16.2, we can do this to avoid the surrounding container div:
render() {
return (
<Fragment>
Some text.
<h2>A heading</h2>
More text.
<h2>Another heading</h2>
Even more text.
</Fragment>
);
}
In either case, we still need need a container element surround the inner elements.
My question is, why is using a Fragment
preferable? Does it help with performance? If so, why? Would love some insight.
div
s in the middle makes it hard to keep the desired layout while extracting logical components.You can find the descriptions of some other use cases in this React issue: Add fragment API to allow returning multiple components from render