react-doctor/jsx-curly-brace-presence
Pick a consistent quoting style for JSX literal values and drop redundant curly braces around plain strings.
- Status
- Active
- Category
- Architecture
- Assessment
- Evidence-required risk
- Required evidence
- source code, repository context
- Default configuration
- Disabled until configured
- Default severity
- warn
Show technical metadata
- Scope
- All supported frameworks
- Active when
- off by default (opt-in)
- Requirements
- react
- Priority
- 8 (P3)
- Source
- oxlint-plugin-react-doctor
- Rule set
- oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
- Documentation
- Official documentation
Validation prompt
Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.
With the default modes (props "never", children "never", propElementValues "ignore"), fires when a JSX attribute or child wraps a plain string literal or single-quasi template in curly braces that add nothing: e.g. prop={'bar'} or <App>{'foo'}</App>: and also flags element/fragment children like <App>{<myApp/>}</App>. It stays silent for whitespace-only braces, line breaks, HTML entities (·), \u escapes, /* */ comments, sibling-adjacent containers, and script-tag children; for children it also ignores strings containing <>{}\ that JSX text cannot hold, plus any single template-literal child carrying a quote, while for props it instead ignores values mixing both quote types. Note the asymmetry: props with <>{}\ DO fire (e.g. <Box mb={'1rem {}'} /> and prop={"< style: true >"}), and children with both quote types DO fire (e.g. <App>{'foo "bar"'}</App>).
Suppress when: a brace-wrapped literal kept intentionally for readability or to sit beside an adjacent {expr} sibling: confirm the surrounding children before suppressing, since this is a stylistic preference, not a bug.
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, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.
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 condition. It is not a pass or false positive.
Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.
Fix prompt
Apply this candidate correction only after the required evidence confirms the risk.
In "never" mode, strip the redundant braces and quotes: change prop={'bar'} to prop="bar" and <App>{'foo'}</App> to <App>foo</App>; for a wrapped element use <App><myApp/></App>. Leave braces in place for whitespace-only content, line breaks, HTML entities, \u escapes, comments, or sibling-adjacent containers; for children also keep them when the text holds <>{}\ characters, and for props keep them when the value mixes both quote types. In "always" mode, do the inverse and wrap the literal in { }. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-curly-brace-presence
Repository-wide copy prompt
Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.
Show repository-wide prompt
Fix every confirmed react-doctor/jsx-curly-brace-presence diagnostic in the current repository.
Required change:
- In "never" mode, strip the redundant braces and quotes: change prop={'bar'} to prop="bar" and <App>{'foo'}</App> to <App>foo</App>; for a wrapped element use <App><myApp/></App>. Leave braces in place for whitespace-only content, line breaks, HTML entities, \u escapes, comments, or sibling-adjacent containers; for children also keep them when the text holds <>{}\ characters, and for props keep them when the value mixes both quote types. In "always" mode, do the inverse and wrap the literal in { }. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-curly-brace-presence.
Validation before editing:
With the default modes (props "never", children "never", propElementValues "ignore"), fires when a JSX attribute or child wraps a plain string literal or single-quasi template in curly braces that add nothing: e.g. prop={'bar'} or <App>{'foo'}</App>: and also flags element/fragment children like <App>{<myApp/>}</App>. It stays silent for whitespace-only braces, line breaks, HTML entities (·), \u escapes, /* */ comments, sibling-adjacent containers, and script-tag children; for children it also ignores strings containing <>{}\ that JSX text cannot hold, plus any single template-literal child carrying a quote, while for props it instead ignores values mixing both quote types. Note the asymmetry: props with <>{}\ DO fire (e.g. <Box mb={'1rem {}'} /> and prop={"< style: true >"}), and children with both quote types DO fire (e.g. <App>{'foo "bar"'}</App>).
Suppress when: a brace-wrapped literal kept intentionally for readability or to sit beside an adjacent {expr} sibling: confirm the surrounding children before suppressing, since this is a stylistic preference, not a bug.
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.
- Confirm this rule is enabled for the project:
off by default (opt-in).
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.