`react-doctor/react-router-no-invalid-absolute-child-path`

Absolute child path escapes its parent

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-invalid-absolute-child-path. 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

<Route path="/dashboard" element={<Dashboard />}>
  <Route path="/reports" element={<Reports />} />
</Route>

Corrected pattern

<Route path="/dashboard" element={<Dashboard />}>
  <Route path="reports" element={<Reports />} />
</Route>

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-invalid-absolute-child-path diagnostic in the current repository. Required change: - Make the child path relative, or prefix its absolute path with the complete parent route path.

Reference transformation:Before:

<Route path="/dashboard" element={<Dashboard />}>
  <Route path="/reports" element={<Reports />} />
</Route>

After:

<Route path="/dashboard" element={<Dashboard />}>
  <Route path="reports" element={<Reports />} />
</Route>

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-invalid-lazy-route-properties: Immutable route property returned from lazy
react-doctor/react-router-no-invalid-splat-path: Invalid splat route path
react-doctor/react-router-no-loader-request-body: Loader reads a request body
react-doctor/react-router-no-middleware-response-body-consumption: Middleware consumes the outgoing response body
react-doctor/react-router-no-multiple-blockers: Multiple blockers in one component

react-doctor/react-router-no-invalid-absolute-child-path