react-doctor/no-controlled-input-value-without-state-update
Controlled input value is a fixed literal
- Category: Bugs
- Severity: warn
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: always
- Tags: react-jsx-only
- Default: Enabled
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/no-controlled-input-value-without-state-update. 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
<input value="fixed" onChange={handleChange} />Corrected pattern
<input value={draft} onChange={(event) => setDraft(event.target.value)} />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
Reference transformation:Before:react-doctor/no-controlled-input-value-without-state-update diagnostic in the current repository.
Required change:
- Drive the input's value from state (const [value, setValue] = useState(...)) that onChange updates, or drop value if the field is meant to be read-only.<input value="fixed" onChange={handleChange} /><input value={draft} onChange={(event) => setDraft(event.target.value)} />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.
- 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.
Related rules
More Bugs rules from the rules reference:
react-doctor/no-create-context-in-render: Move createContext to module scope so its Context identity stays stable across rendersreact-doctor/no-create-object-url-in-render: Object URL is created during renderreact-doctor/no-create-ref-in-function-component: createRef in function componentreact-doctor/no-create-store-in-render: Hoist the store/atom/observable construction to module scope: const store = create(...) outside the component.react-doctor/no-danger-with-children: Use either children or dangerouslySetInnerHTML on an element, never both.