# `react-doctor/self-closing-comp`

Use the self-closing form `<X />` for elements with no children.

- **Status:** Active
- **Category:** Architecture
- **Assessment:** Evidence-required risk
- **Required evidence:** source code, repository context
- **Default configuration:** Disabled until configured
- **Default severity:** warn
- **Scope:** All supported frameworks
- **Active when:** off by default (opt-in)
- **Requirements:** react
- **Priority:** 12 (P3)
- **Source:** oxlint-plugin-react-doctor
- **Rule set:** oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
- **Documentation:** [Official documentation](https://oxc.rs/docs/guide/usage/linter/rules/react/self-closing-comp)

## Validation prompt

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

Fires on a JSXElement that carries an explicit closing tag yet has no real children: either zero children or a single JSXText child that is whitespace containing a newline (`<X>\n</X>`): meaning `<X />` would render identically. Custom components (PascalCase, member like `Foo.Bar`, or namespaced) and lowercase HTML tags are both flagged, but the `component` and `html` settings can independently silence either group. False positive / non-trigger to watch: single-line whitespace with no newline (`<X> </X>`), an expression child like `<div>{' '}</div>`, and entity children like `<div> </div>` are all intentionally left alone: only flag when the element is genuinely childless.

## 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, explicit repository policy, relevant exceptions, and required rendered or runtime evidence before deciding the occurrence. This page’s Assessment and Required evidence fields define the review contract.

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

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 or expiry condition. It is not a pass or false positive.

## Fix prompt

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

Collapse the empty element to its self-closing form, dropping the redundant closing tag: rewrite `<Hello name="John"></Hello>` (or the multi-line `<div className="content">\n</div>`) as `<Hello name="John" />` and `<div className="content" />`. This is a purely stylistic equivalence: behavior and output are unchanged, so it is safe to apply mechanically. If a single space is intentional content, use `<X> </X>` (no newline) or `<X>{' '}</X>`, which the rule already permits. See https://oxc.rs/docs/guide/usage/linter/rules/react/self-closing-comp

## Repository-wide copy prompt

Use this only for a repository-wide pass after validating each occurrence. For one occurrence, use the occurrence-level guidance above.

````text
Fix every confirmed `react-doctor/self-closing-comp` diagnostic in the current repository.

Required change:
- Collapse the empty element to its self-closing form, dropping the redundant closing tag: rewrite `<Hello name="John"></Hello>` (or the multi-line `<div className="content">\n</div>`) as `<Hello name="John" />` and `<div className="content" />`. This is a purely stylistic equivalence: behavior and output are unchanged, so it is safe to apply mechanically. If a single space is intentional content, use `<X> </X>` (no newline) or `<X>{' '}</X>`, which the rule already permits. See https://oxc.rs/docs/guide/usage/linter/rules/react/self-closing-comp.

Validation before editing:
Fires on a JSXElement that carries an explicit closing tag yet has no real children: either zero children or a single JSXText child that is whitespace containing a newline (`<X>\n</X>`): meaning `<X />` would render identically. Custom components (PascalCase, member like `Foo.Bar`, or namespaced) and lowercase HTML tags are both flagged, but the `component` and `html` settings can independently silence either group. False positive / non-trigger to watch: single-line whitespace with no newline (`<X> </X>`), an expression child like `<div>{' '}</div>`, and entity children like `<div> </div>` are all intentionally left alone: only flag when the element is genuinely childless.

Constraints:
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.
- Confirm this rule is enabled for the project: `off by default (opt-in)`.

Assessment:
- Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
- Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
- A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears from changed code.
- Run an unfiltered scan of the affected scope before claiming no cross-category regression.
- Report the files changed and any checks you could not run.
````