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

react-doctor/no-placeholder-persona-copy

Page renders a placeholder persona

  • Category: Maintainability
  • Severity: warn
  • Source: oxlint-plugin-react-doctor
  • Framework: global
  • Enabled when: always
  • Tags: design, test-noise
  • 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-placeholder-persona-copy. 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 Page = () => (
  <main>
    <h1>Our customers</h1>
    <p>Jane Doe</p>
    <p>Product Designer</p>
  </main>
);

Corrected pattern

const Page = () => (
  <main>
    <h1>Our customers</h1>
    <p>Demo profile</p>
    <p>Product Designer</p>
  </main>
);

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-placeholder-persona-copy diagnostic in the current repository. Required change: - Replace placeholder identities with approved, context-specific demo data. If none exists, label the surface as a demo instead of inventing a customer.
Reference transformation:Before:
const Page = () => (
  <main>
    <h1>Our customers</h1>
    <p>Jane Doe</p>
    <p>Product Designer</p>
  </main>
);
After:
const Page = () => (
  <main>
    <h1>Our customers</h1>
    <p>Demo profile</p>
    <p>Product Designer</p>
  </main>
);
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: