Update RouteMatchType.md

[jonasantonelli]

add staticData property to the RouteMatchType

Summary by CodeRabbit

• New Features

  • Route matching now provides access to static route data through a new property on the RouteMatch interface, giving developers additional route configuration information during route matching operations.

• Documentation

  • Updated API reference documentation for the RouteMatch interface to reflect the new capability.

[coderabbitai]

Walkthrough

Documentation updated to add a new staticData property of type StaticDataRouteOption to the RouteMatch interface, expanding the publicly exposed route match data structure.

Changes

Cohort / File(s)	Summary
Documentation: RouteMatch Interface docs/router/framework/react/api/router/RouteMatchType.md	Added staticData: StaticDataRouteOption property to RouteMatch interface documentation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single documentation file with straightforward property addition
• No logic changes or code modifications
• Minimal context needed for verification

Poem

🐰 A property so neat, now documented with care,
staticData joins the RouteMatch affair,
Routes now richer, their stories told true,
Hopping through docs, our interface anew! 📚✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	The pull request title "Update RouteMatchType.md" is vague and generic. While it correctly identifies the file being modified, it fails to convey the specific nature of the change. The actual modification is adding a new staticData property to the RouteMatch interface, but the title uses only the generic term "Update" without describing what aspect of the file was modified. A teammate scanning the pull request history would not understand from this title alone that the change involves adding a new property to the interface.	Consider revising the title to be more specific about the actual change, such as "Add staticData property to RouteMatchType" or "Add staticData property to RouteMatch interface in RouteMatchType.md". This would make the title more descriptive and informative about the primary change being introduced, helping teammates quickly understand the pull request's purpose without needing to review the details.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/router/framework/react/api/router/RouteMatchType.md (1)

28-28: Add explanation and link for the staticData property.

The new staticData property is added without any documentation explaining its purpose, when it's populated, or what StaticDataRouteOption represents. This leaves users unclear about how to use this property.

Consider adding:

1. An explanation of what staticData contains and its purpose
2. A link to the StaticDataRouteOption type definition/documentation (using relative doc links per guidelines)
3. An example showing typical usage

Additionally, clarify whether this property is always present (required) or sometimes absent (optional with ?).

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a62499 and d9ca7f6.

📒 Files selected for processing (1)

• docs/router/framework/react/api/router/RouteMatchType.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (AGENTS.md)

Use internal docs links relative to the docs/ folder (e.g., ./guide/data-loading)

Files:

• docs/router/framework/react/api/router/RouteMatchType.md

docs/{router,start}/**

📄 CodeRabbit inference engine (AGENTS.md)

Place router docs under docs/router/ and start framework docs under docs/start/

Files:

• docs/router/framework/react/api/router/RouteMatchType.md