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

react-doctor/no-numbered-section-markers

Styled numbers are used as section decoration

  • 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-numbered-section-markers. 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>
    <section>
      <span className="text-xs font-mono">02</span>
      <h2>Explore</h2>
    </section>
    <section>
      <span className="text-xs font-mono">09</span>
      <h2>Refine</h2>
    </section>
  </main>
);

Corrected pattern

const Page = () => (
  <main>
    <section><h2>Explore</h2></section>
    <section><h2>Refine</h2></section>
  </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-numbered-section-markers diagnostic in the current repository. Required change: - Remove decorative section numbering unless the sequence communicates real progress or ordered steps.
Reference transformation:Before:
const Page = () => (
  <main>
    <section>
      <span className="text-xs font-mono">02</span>
      <h2>Explore</h2>
    </section>
    <section>
      <span className="text-xs font-mono">09</span>
      <h2>Refine</h2>
    </section>
  </main>
);
After:
const Page = () => (
  <main>
    <section><h2>Explore</h2></section>
    <section><h2>Refine</h2></section>
  </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: