New
Introducing React Bench, see how different models perform on React code

react-doctor/no-radial-halo

Saturated radial halo on a dark surface

  • Category: Maintainability
  • Severity: warn
  • Source: oxlint-plugin-react-doctor
  • Framework: global
  • Enabled when: always
  • Tags: design, test-noise, react-jsx-only
  • Default: Disabled until configured

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/no-radial-halo. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

const Surfaces = () => (
  <>
    <div
      style={{
        backgroundColor: "#020617",
        backgroundImage:
          "radial-gradient(circle, #2563ebcc 0, transparent 24px)",
      }}
    />
    <div
      style={{
        backgroundColor: "#020617",
        backgroundImage:
          "radial-gradient(circle, #2563ebcc 0, transparent 25px)",
      }}
    />
  </>
);

Corrected pattern

const Surfaces = () => (
  <>
    <div style={{ backgroundColor: "#020617" }} />
    <div style={{ backgroundColor: "#020617" }} />
  </>
);

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/no-radial-halo diagnostic in the current repository. Required change: - Use restrained surface contrast, product-specific imagery, or a subtler accent instead of a saturated radial halo on a dark page.
Reference transformation:Before:
const Surfaces = () => (
  <>
    <div
      style={{
        backgroundColor: "#020617",
        backgroundImage:
          "radial-gradient(circle, #2563ebcc 0, transparent 24px)",
      }}
    />
    <div
      style={{
        backgroundColor: "#020617",
        backgroundImage:
          "radial-gradient(circle, #2563ebcc 0, transparent 25px)",
      }}
    />
  </>
);
After:
const Surfaces = () => (
  <>
    <div style={{ backgroundColor: "#020617" }} />
    <div style={{ backgroundColor: "#020617" }} />
  </>
);
Constraints: - Confirm the reported code matches the Before pattern. - 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. - Use existing brand assets, product facts, content, and design tokens. - Do not invent claims, customer data, typefaces, or artwork. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Maintainability rules from the rules reference:

  • react-doctor/no-react-children: Pass children as props or render them directly instead of calling React.Children methods.
  • react-doctor/no-react-dom-deprecated-apis: Switch the legacy `react-dom` root API (`render` / `hydrate` / `unmountComponentAtNode`) to `createRoot` / `hydrateRoot` / `root.unmount()` from `react-dom/client`. Replace `findDOMNode` with a ref. The whole `react-dom/test-utils` entry point is removed in React 19 — use `act` from `react` and `fireEvent` / `render` from `@testing-library/react`. Only enabled on projects detected as React 18+.
  • react-doctor/no-react19-deprecated-apis: Pass `ref` as a regular prop on function components — `forwardRef` is no longer needed in React 19+. Replace `useContext(X)` with `use(X)` for branch-aware context reads. Only enabled on projects detected as React 19+.
  • react-doctor/no-redundant-display-class: Redundant display utility
  • react-doctor/no-redundant-should-component-update: Drop shouldComponentUpdate when extending PureComponent, or extend React.Component if custom comparison logic is genuinely needed.