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

react-doctor/no-whole-object-default-losing-per-key-defaults

Whole-object param default loses per-key defaults

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

Validate the diagnostic

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

Confirm the reported code matches react-doctor/no-whole-object-default-losing-per-key-defaults. 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 read = ({ color, size } = { color: "blue", size: "md" }) => ({
  color,
  size,
});

Corrected pattern

const read = (
  { color = "blue", size = "md" } = {},
) => ({ color, size });

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-whole-object-default-losing-per-key-defaults diagnostic in the current repository. Required change: - A whole-object parameter default applies only when the argument is omitted entirely, so a partial argument makes every omitted key undefined. Move each fallback onto its own binding instead: ({ a = 1, b = false } = {}).
Reference transformation:Before:
const read = ({ color, size } = { color: "blue", size: "md" }) => ({
  color,
  size,
});
After:
const read = (
  { color = "blue", size = "md" } = {},
) => ({ color, size });
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: