# `react-doctor/no-namespace`

Drop the namespace and use a plain (Pascal-cased) component or DOM tag.

- **Status:** Active
- **Category:** Correctness
- **Assessment:** Evidence-required risk
- **Required evidence:** source code
- **Default configuration:** Enabled
- **Default severity:** warn
- **Scope:** All supported frameworks
- **Active when:** always
- **Requirements:** react
- **Priority:** 28 (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/no-namespace)

## Validation prompt

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

Fires on JSX elements whose tag is a namespaced name with a colon separator (`<ns:Foo />`), and on `React.createElement` calls whose first argument is a string literal containing a colon (`React.createElement("ns:foo")`): React supports neither and treats them as runtime errors. Member-expression tags using a dot (`<Object.TestComponent />`, `React.createElement("object.test")`) are intentionally NOT flagged, and `createElement` with a non-string-literal first arg (a variable, null, boolean, or object) is never inspected.

Suppress when: the createElement check is purely static, so a colon-bearing type passed through a variable rather than an inline string literal slips past it: and conversely, an inline literal like `React.createElement("data:image")` is flagged even when no JSX is involved.

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

Remove the namespace prefix and reference the component or DOM tag directly: rewrite `<ns:Foo />` as `<Foo />` and `React.createElement("ns:foo")` as `React.createElement("foo")` (or a Pascal-cased component reference). If you need to render a true XML namespace like SVG, use the standard JSX tag React maps for you (`<circle />` inside `<svg>`), not the `svg:` prefix. See https://oxc.rs/docs/guide/usage/linter/rules/react/no-namespace

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

Required change:
- Remove the namespace prefix and reference the component or DOM tag directly: rewrite `<ns:Foo />` as `<Foo />` and `React.createElement("ns:foo")` as `React.createElement("foo")` (or a Pascal-cased component reference). If you need to render a true XML namespace like SVG, use the standard JSX tag React maps for you (`<circle />` inside `<svg>`), not the `svg:` prefix. See https://oxc.rs/docs/guide/usage/linter/rules/react/no-namespace.

Validation before editing:
Fires on JSX elements whose tag is a namespaced name with a colon separator (`<ns:Foo />`), and on `React.createElement` calls whose first argument is a string literal containing a colon (`React.createElement("ns:foo")`): React supports neither and treats them as runtime errors. Member-expression tags using a dot (`<Object.TestComponent />`, `React.createElement("object.test")`) are intentionally NOT flagged, and `createElement` with a non-string-literal first arg (a variable, null, boolean, or object) is never inspected.

Suppress when: the createElement check is purely static, so a colon-bearing type passed through a variable rather than an inline string literal slips past it: and conversely, an inline literal like `React.createElement("data:image")` is flagged even when no JSX is involved.

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