Skip to content

Conversation

Floriferous
Copy link

@Floriferous Floriferous commented Aug 26, 2025

The docs for router context explain how to set it up, and how to use it in loaders, but it doesn't explain how to simply use it in react components. I'm not even sure this is the right way to do it?

Happy to make it better if necessary.

Summary by CodeRabbit

  • Documentation
    • Added two practical examples to the React guide’s "Using the Router Context" section demonstrating how to access and render values from a route context (e.g., a user ID).
    • Examples are placed in two locations for easier discovery and reference.
    • No runtime behavior or public API changes.

Copy link
Contributor

coderabbitai bot commented Aug 26, 2025

Walkthrough

Adds two documentation examples to the React Router Context guide demonstrating usage of Route.useRouteContext() to access routeContext.user.id. Documentation-only; no runtime code, behavior, or public API changes.

Changes

Cohort / File(s) Summary
Docs: Router Context (React)
docs/router/framework/react/guide/router-context.md
Inserted two code snippets showing Route.useRouteContext() (imported from @tanstack/react-router) used inside a Todos component to obtain routeContext and render routeContext.user.id. Documentation-only; no API or runtime changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibble docs with careful bite,
Two snippets hop into the light.
A hook that finds its context true—
Route says who, and user too.
My paws applaud this tidy write. 🥕

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between cf0aa6e and 244ac55.

📒 Files selected for processing (1)
  • docs/router/framework/react/guide/router-context.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/router/framework/react/guide/router-context.md
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the documentation Everything documentation related label Aug 26, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
docs/router/framework/react/guide/router-context.md (3)

106-107: Avoid redefining Route inconsistently with the earlier example or clearly make this block standalone

This block redefines Route right after an earlier snippet already defined it. That can be confusing when reading sequentially. Either:

  • make this block standalone (keep the redefinition and add the missing import as in the previous comment), or
  • assume the prior Route definition and remove these two lines, showing only component usage.

If you prefer the latter, apply:

-export const Route = createFileRoute('/todos')({ component: Todos });
-
 function Todos() {

101-102: Tighten the phrasing to highlight type-safety via from: Route.id

Minor copy edit to make the benefit explicit and align with Router docs terminology.

-You can use it in your components with the `useRouteContext` hook:
+You can use it in your components with the `useRouteContext` hook. Passing `{ from: Route.id }` ensures the context is typed to this route’s merged context:

109-111: Prefer destructuring for clarity in examples

Small readability tweak; also mirrors common patterns in the docs.

-function Todos() {
-  const routeContext = useRouteContext({ from: Route.id });
-  return <div>Todos from {routeContext.user.id}</div>
-}
+function Todos() {
+  const { user } = useRouteContext({ from: Route.id })
+  return <div>Todos from {user.id}</div>
+}
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 8134650 and 2537435.

📒 Files selected for processing (1)
  • docs/router/framework/react/guide/router-context.md (1 hunks)

@Floriferous
Copy link
Author

Floriferous commented Aug 26, 2025

This is also a helpful pattern, but again maybe there is already something built-in?

export const Route = createRootRouteWithContext<MyRouterContext>()({
  component: RootComponent, // Initialized router context in here
});

// Add this to easily access your root context across your app
export function useRootRouteContext() {
  return Route.useRouteContext();
}

Can add this in if it makes sense.

@Floriferous
Copy link
Author

Or maybe the best way is this:

import { useRouteContext } from '@tanstack/react-router';

export function useRootRouteContext() {
  return useRouteContext({ from: "__root__" });
}

You can use it in your components with the `useRouteContext` hook:

```tsx
import { createFileRoute, useRouteContext } from '@tanstack/react-router';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you need this import since you are using Route.useRouteContext

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Everything documentation related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants