react-doctor/tanstack-start-route-property-order
Follow the order: params/validateSearch → loaderDeps → context → beforeLoad → loader → head. See https://tanstack.com/router/latest/docs/eslint/create-route-property-order
- Status
- Active
- Category
- TanStack Start
- Assessment
- Evidence-required risk
- Required evidence
- source code
- Default configuration
- Enabled
- Default severity
- error
Show technical metadata
- Scope
- TanStack Start
- Active when
- framework=tanstack-start and capabilities=tanstack-start
- Requirements
- tanstack-start
- Tags
- test-noise
- Priority
- 25 (P3)
- Source
- oxlint-plugin-react-doctor
- Rule set
- oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
Validation prompt
Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.
Fires (error severity) when properties on a createFileRoute/createRoute/createRootRoute options object appear out of the canonical order: params, validateSearch, loaderDeps, search.middlewares, ssr, context, beforeLoad, loader, onEnter, onStay, onLeave, head, scripts, headers, remountDeps. Only those keys are compared; spreads, computed keys, and unknown keys are skipped. The first out-of-order key is reported.
Evidence boundary
The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.
Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.
Record one outcome:
- Confirmed failure: The required evidence establishes the violation.
- Rejected: A documented exception or false-positive predicate applies.
- Needs evidence: Named evidence can still be collected.
- Unavailable: Required evidence cannot be collected in this run.
- Waived with evidence: An authorized, scoped exception applies to an established failure.
- Observation: The review records an optional tradeoff without claiming a defect.
A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.
Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.
Fix prompt
Apply this candidate correction only after the required evidence confirms the risk.
Reorder the options object so each property appears in canonical sequence (params → loaderDeps → context → beforeLoad → loader → head). Each step contributes to the inferred context/loader-data type that later steps consume, so wrong order breaks type inference downstream. See https://tanstack.com/router/latest/docs/eslint/create-route-property-order
Repository-wide copy prompt
Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.
Show repository-wide prompt
Fix every confirmed react-doctor/tanstack-start-route-property-order diagnostic in the current repository.
Required change:
- Reorder the options object so each property appears in canonical sequence (params → loaderDeps → context → beforeLoad → loader → head). Each step contributes to the inferred context/loader-data type that later steps consume, so wrong order breaks type inference downstream. See https://tanstack.com/router/latest/docs/eslint/create-route-property-order.
Validation before editing:
Fires (error severity) when properties on a createFileRoute/createRoute/createRootRoute options object appear out of the canonical order: params, validateSearch, loaderDeps, search.middlewares, ssr, context, beforeLoad, loader, onEnter, onStay, onLeave, head, scripts, headers, remountDeps. Only those keys are compared; spreads, computed keys, and unknown keys are skipped. The first out-of-order key is reported.
Constraints:
- 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:
framework=tanstack-start and capabilities=tanstack-start.
Assessment:
- Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
- Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
- A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.
Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears from changed code.
- Run an unfiltered scan of the affected scope before claiming no cross-category regression.
- Report the files changed and any checks you could not run.