Fragments should not be used when there is 1 child

Docs > Code Analysis > Static Analysis Rules > Fragments should not be used when there is 1 child

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Metadata

ID: tsx-react/no-redundant-fragments

Language: TypeScript

Severity: Warning

Category: Code Style

Description

This rule emphasizes that React Fragments should not be used when there is only one child within the component. React Fragments are a useful feature for grouping a list of children without adding extra nodes to the DOM. However, when there is only a single child, the use of Fragments is unnecessary and can lead to cluttered and confusing code.

To avoid violating this rule, remove the Fragment (<>...</>) when you have only one child in your component. Instead of wrapping a single child with a Fragment, you can return the child directly.

Non-Compliant Code Examples

export default function Menu() {
  return (
    <>
      <MenuText />
    </>
  );
}

function MenuText() {
  return (
    <h1>
    <>Menu</>
    </h1>
  );
}

Compliant Code Examples

export default function Menu() {
  return <MenuText />;
}

function MenuText() {
  return <h1>Menu</h1>;
}