`react-doctor/no-unguarded-numeric-input-parse`

Unguarded numeric parse of an input value

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: always
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/no-unguarded-numeric-input-parse. 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 onChange={(event) => setCount(Number(event.target.value))} />

Corrected pattern

<input
  onChange={(event) =>
    setCount(event.target.value ? Number(event.target.value) : undefined)
  }
/>;

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-unguarded-numeric-input-parse diagnostic in the current repository. Required change: - Guard Number(e.target.value) / parseInt(e.target.value) against empty and NaN before storing it. Number('') is 0 and Number('abc') is NaN, both of which silently ship a wrong value.

Reference transformation:Before:

<input onChange={(event) => setCount(Number(event.target.value))} />

After:

<input
  onChange={(event) =>
    setCount(event.target.value ? Number(event.target.value) : undefined)
  }
/>;

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.

More Bugs rules from the rules reference:

react-doctor/no-unguarded-throwing-parse-call: Unguarded call to a throwing parse API
react-doctor/no-unknown-property: Disallow unknown or mis-cased DOM attributes in JSX, like class instead of className.
react-doctor/no-unsafe: Replace UNSAFE_componentWillMount / WillReceiveProps / WillUpdate with their modern lifecycle equivalents.
react-doctor/no-unsafe-json-parse: Unsafe JSON.parse dereference
react-doctor/no-whole-object-default-losing-per-key-defaults: Whole-object param default loses per-key defaults

react-doctor/no-unguarded-numeric-input-parse