# `react-doctor/forbid-elements`

Replace each configured forbidden element with its sanctioned component or wrapper.

- **Status:** Active
- **Category:** Architecture
- **Assessment:** Evidence-required risk
- **Required evidence:** source code, repository context
- **Default configuration:** Enabled
- **Default severity:** warn
- **Scope:** All supported frameworks
- **Active when:** always
- **Requirements:** react
- **Priority:** 16 (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/forbid-elements)

## Validation prompt

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

Fires only when the `forbidElements.forbid` setting is non-empty, then reports any JSX opening element whose flattened name (e.g. `button`, `Modal`, `dotted.Component`) is in that list, plus matching `React.createElement(...)` / bare `createElement(...)` calls whose first argument resolves to a forbidden name. createElement string args only match if they look like a real DOM tag: lowercase first char and no dots: while identifier args match only when PascalCase or leading-underscore, and member expressions match by flattened name.

Suppress when: it cannot tell apart two distinct things sharing a name, so a forbidden `button` entry also flags a legitimate local component or third-party export that happens to be named identically.

## 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.

Swap the forbidden element for the sanctioned replacement named in the finding's message, e.g. replace `<button>` with your design-system `<Button>` (and likewise rewrite `React.createElement("button", ...)` to `React.createElement(Button, ...)`). If a flagged usage is a genuine, intentional exception, remove that entry from the `forbidElements.forbid` setting or add an inline disable with a written justification rather than suppressing project-wide. See https://oxc.rs/docs/guide/usage/linter/rules/react/forbid-elements

## 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/forbid-elements` diagnostic in the current repository.

Required change:
- Swap the forbidden element for the sanctioned replacement named in the finding's message, e.g. replace `<button>` with your design-system `<Button>` (and likewise rewrite `React.createElement("button", ...)` to `React.createElement(Button, ...)`). If a flagged usage is a genuine, intentional exception, remove that entry from the `forbidElements.forbid` setting or add an inline disable with a written justification rather than suppressing project-wide. See https://oxc.rs/docs/guide/usage/linter/rules/react/forbid-elements.

Validation before editing:
Fires only when the `forbidElements.forbid` setting is non-empty, then reports any JSX opening element whose flattened name (e.g. `button`, `Modal`, `dotted.Component`) is in that list, plus matching `React.createElement(...)` / bare `createElement(...)` calls whose first argument resolves to a forbidden name. createElement string args only match if they look like a real DOM tag: lowercase first char and no dots: while identifier args match only when PascalCase or leading-underscore, and member expressions match by flattened name.

Suppress when: it cannot tell apart two distinct things sharing a name, so a forbidden `button` entry also flags a legitimate local component or third-party export that happens to be named identically.

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.

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.
````