Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

docs(router): align RouteMatch API reference with the current public contract

Open Beginner friendly
#7,789 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@soheilnikroo is already working on this.

Since Jul 12, 2026.

  • #7800 by @soheilnikroo — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
documentation

Research direction

Start with docs/router/api/router/RouteMatchType.md and compare it against packages/router-core/src/Matches.ts, using the public contract described in the issue as the guide. Remove obsolete and internal fields, add the specified public fields and cause value, and review the complete page for accuracy. Done means the reference matches the intentional public RouteMatch API without lifecycle-only state.

Written by the indexing model from the issue text.

Description

Goal

Bring the RouteMatch API reference in line with the current public contract.

Scope

  • Remove obsolete showPending and fetchedAt entries from docs/router/api/router/RouteMatchType.md.
  • Add fullPath using its route-specific type, Route['fullPath'].
  • Add index and explain its ordering within the matched route array.
  • Update cause to include 'preload'.
  • Keep internal and lifecycle-specific match state out of the reference, including displayPendingPromise, fetchCount, preload, invalid, headers, and globalNotFound.
  • Review the complete page against packages/router-core/src/Matches.ts so the reference describes the intentional public API.

Related Work

This continues the RouteMatch reference update started in #4894

Dominant language
TypeScript
Stars
15.1k
Forks
1.9k
Avg merge
1d 17h
Merged PRs (30d)
134

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TanStack/router

All issues in TanStack/router

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.