react-doctor/jsx-no-useless-fragment

Drop the fragment when it wraps a single child or holds multiple children directly under an HTML tag.

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on a fragment (<></>, <Fragment>, or <React.Fragment>) with fewer than two meaningful children: whitespace-only text containing a newline is treated as padding and ignored, so <><Foo /></> and <div><>foo</></div> both trip the single-child path. It also fires, separately, on a fragment with 2+ children sitting directly inside a lowercase HTML element (e.g. <div><>{"a"}{"b"}</></div>), since the element can hold the children directly; this HTML-element branch only triggers when the single-child check did not already report. Several escape hatches suppress it: a key attribute, any {call()} child (e.g. <>{items.map(...)}</>), a single text-only child whose parent is not itself JSX (content={<>text</>}), and allowExpressions: true which permits <>{expr}</>.

Suppress when: a single-child fragment kept intentionally to widen the return type to ReactNode or to keep a conditional symmetric (show ? <>{children}</> : null): confirm only when the wrapper is genuinely redundant.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

For a single-child fragment, remove the wrapper and return its lone child directly: <><Foo /></> becomes <Foo />, and <div><>foo</></div> becomes <div>foo</div>. For the multi-child-inside-HTML case, drop the fragment and let the element hold the children: <div><>{"a"}{"b"}</></div> becomes <div>{"a"}{"b"}</div>. For an empty <></> or <Fragment />, delete it entirely or replace it with the value it was standing in for; if a single-child wrapper is deliberate (broadening the return type to ReactNode or keeping branches symmetric), enable allowExpressions for the <>{expr}</> case or leave it as-is rather than collapsing. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-no-useless-fragment

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.