`react-doctor/react-router-no-unsynchronized-search-params-mutation`

Search params mutated without navigation

Category: Bugs
Severity: error
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react-router
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/react-router-no-unsynchronized-search-params-mutation. 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 selectPage = (page) => {
  searchParams.set("page", String(page));
  setSearchParams(searchParams);
};

Corrected pattern

const selectPage = (page) => {
  setSearchParams((current) => {
    const next = new URLSearchParams(current);
    next.set("page", String(page));
    return next;
  });
};

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/react-router-no-unsynchronized-search-params-mutation diagnostic in the current repository. Required change: - Clone the URLSearchParams value, mutate the clone, and return or pass it to setSearchParams.

Reference transformation:Before:

const selectPage = (page) => {
  searchParams.set("page", String(page));
  setSearchParams(searchParams);
};

After:

const selectPage = (page) => {
  setSearchParams((current) => {
    const next = new URLSearchParams(current);
    next.set("page", String(page));
    return next;
  });
};

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. - Confirm this rule is enabled for the project: react-router. 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/react-router-no-use-loader-data-in-error-ui: Error UI assumes loader data exists
react-doctor/react-router-require-root-error-boundary: Root route lacks an error boundary
react-doctor/react-router-resource-link-requires-reload: Resource link intercepted as navigation
react-doctor/react-router-return-navigation-promise-in-transition: Transition drops a navigation promise
react-doctor/react-router-server-middleware-return-response: Server middleware drops the Response

react-doctor/react-router-no-unsynchronized-search-params-mutation