{"componentChunkName":"component---src-templates-docs-js","path":"/docs/create-fragment.html","result":{"data":{"markdownRemark":{"html":"
\n

Note:

\n

React.addons entry point is deprecated as of React v15.5. We now have first class support for fragments which you can read about here.

\n
\n

Importing

\n
import createFragment from 'react-addons-create-fragment'; // ES6\nvar createFragment = require('react-addons-create-fragment'); // ES5 with npm
\n

Overview

\n

In most cases, you can use the key prop to specify keys on the elements you’re returning from render. However, this breaks down in one situation: if you have two sets of children that you need to reorder, there’s no way to put a key on each set without adding a wrapper element.

\n

That is, if you have a component such as:

\n
function Swapper(props) {\n  let children;\n  if (props.swapped) {\n    children = [props.rightChildren, props.leftChildren];\n  } else {\n    children = [props.leftChildren, props.rightChildren];\n  }\n  return <div>{children}</div>;\n}
\n

The children will unmount and remount as you change the swapped prop because there aren’t any keys marked on the two sets of children.

\n

To solve this problem, you can use the createFragment add-on to give keys to the sets of children.

\n

Array<ReactNode> createFragment(object children)

\n

Instead of creating arrays, we write:

\n
import createFragment from 'react-addons-create-fragment';\n\nfunction Swapper(props) {\n  let children;\n  if (props.swapped) {\n    children = createFragment({\n      right: props.rightChildren,\n      left: props.leftChildren\n    });\n  } else {\n    children = createFragment({\n      left: props.leftChildren,\n      right: props.rightChildren\n    });\n  }\n  return <div>{children}</div>;\n}
\n

The keys of the passed object (that is, left and right) are used as keys for the entire set of children, and the order of the object’s keys is used to determine the order of the rendered children. With this change, the two sets of children will be properly reordered in the DOM without unmounting.

\n

The return value of createFragment should be treated as an opaque object; you can use the React.Children helpers to loop through a fragment but should not access it directly. Note also that we’re relying on the JavaScript engine preserving object enumeration order here, which is not guaranteed by the spec but is implemented by all major browsers and VMs for objects with non-numeric keys.

","frontmatter":{"title":"Keyed Fragments","next":null,"prev":null},"fields":{"path":"content/docs/addons-create-fragment.md","slug":"docs/create-fragment.html"}}},"pageContext":{"slug":"docs/create-fragment.html"}},"staticQueryHashes":[]}