`react-doctor/react-router-guard-aborted-handle-error`

Aborted requests are reported as errors

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react-router:7, react-router-framework
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-guard-aborted-handle-error. 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 handleError = (error, { request }) => {
  reportError(error);
};

Corrected pattern

const handleError = (error, { request }) => {
  if (request.signal.aborted) return;
  reportError(error);
};

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-guard-aborted-handle-error diagnostic in the current repository. Required change: - Return early when request.signal.aborted before reporting the error from handleError.

Reference transformation:Before:

const handleError = (error, { request }) => {
  reportError(error);
};

After:

const handleError = (error, { request }) => {
  if (request.signal.aborted) return;
  reportError(error);
};

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:7, react-router-framework. 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-internal-route-anchor: Internal route uses a document navigation
react-doctor/react-router-nested-route-requires-outlet: Nested routes have no Outlet
react-doctor/react-router-no-catch-middleware-next: Middleware catch cannot observe downstream errors
react-doctor/react-router-no-client-module-in-server-render: Client-only module rendered on the server
react-doctor/react-router-no-duplicate-route-id: Duplicate route ID

react-doctor/react-router-guard-aborted-handle-error