`react-doctor/no-dynamic-tailwind-class-fragment`

Tailwind utility is assembled dynamically

Category: Maintainability
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: tailwind
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-dynamic-tailwind-class-fragment. 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

<div className={`text-${tone}-600`} />

Corrected pattern

<div className={tone === "error" ? "text-red-600" : "text-slate-600"} />

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-dynamic-tailwind-class-fragment diagnostic in the current repository. Required change: - Use complete, statically discoverable Tailwind utility strings for each state instead of interpolating part of a class token.

Reference transformation:Before:

<div className={`text-${tone}-600`} />

After:

<div className={tone === "error" ? "text-red-600" : "text-slate-600"} />

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. - Confirm this rule is enabled for the project: tailwind. 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-emoji-heading-decoration: Heading uses emoji as decoration
react-doctor/no-empty-card-shell: Empty semantic element renders as a card
react-doctor/no-excessive-card-surfaces: Page boxes too many groups into cards
react-doctor/no-excessive-centered-copy: Page centers multiple body-copy blocks
react-doctor/no-excessive-font-families: Page mixes too many font families

react-doctor/no-dynamic-tailwind-class-fragment