When returning a number of components from a element’s render methodology, they have to be wrapped in a single mum or dad DOM node:

// Wants a <div> wrapper
return (
  <div> 
    <ChildA />
    <ChildB />
  </div>
);

This additional wrapper <div> within the DOM is usually undesirable. Enter React fragments – a technique to group components with out including additional nodes.

Quick Syntax

The best fragment syntax is:

return (
  <>
    <ChildA />
    <ChildB />
  </>
);

The <></> syntax declares a React fragment. Fragments allow you to skip the wrapper <div>.

Keyed Fragments

Fragments can be keyed to provide baby components a context:

perform Guardian() {
  const objects = ['A', 'B', 'C'];
  
  return (
    <MyFragment>
      {objects.map(merchandise => <Little one key={merchandise} />)} 
    </MyFragment>
  );
}

const MyFragment = React.Fragment;

Keyed fragments are useful for record objects that want a context.

Motivation

Fragments have been launched to scale back additional DOM nodes. Some advantages are:

• Keep away from wrapper nodes in DOM tree
• Semantically group parts collectively
• Key record objects with out including wrappers

This improves render effectivity and semantics.

Utilization Ideas

• Use brief syntax for inline element teams
• Key fragments to supply record merchandise context
• Want fragments over wrapper divs
• Don’t overuse – attempt to preserve parts logically grouped

Fragments are a instrument for cleaner, extra readable element timber.

Abstract

• Fragments allow you to group components with no DOM node
• Gives shorter syntax vs wrapper divs
• Keyed fragments present context for lists
• Improves render effectivity and semantics
• Use judiciously in response to use case

React fragments are a key instrument for constructing element hierarchies. No extra thriller bins!