Refactor route component structure and naming

[imxade]

Summary by CodeRabbit

• Refactor
  • Updated the application’s root structure to provide connection and debugging support consistently across the app.
  • Preserved the existing route content while improving how shared app services are applied.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: aba64d3f-f330-4f27-8a90-44605424704c

📥 Commits

Reviewing files that changed from the base of the PR and between 46e07fa and d9cab02.

📒 Files selected for processing (1)

• src/routes/__root.tsx

---

Walkthrough

The root route now separates provider composition from route rendering. AppProviders supplies the provider shell, and RootComponent renders the route content.

Changes

Root provider composition

Layer / File(s)	Summary
Provider shell wiring src/routes/__root.tsx	AppProviders wraps route children with ConnectionProvider and DebugProvider. The route uses AppProviders as shellComponent and RootComponent as component.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels: Typescript Lang

Suggested reviewers: pinjinx

Poem

A rabbit checks the provider nest,
AppProviders wraps the rest.
RootComponent takes the stage,
Clean route wiring fills the page.
Hop, hop—types align just right!

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}