docs: note layout routes require an Outlet element - #7899
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe React and Solid routing guides now note that generated layout route components do not include ChangesLayout route documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
By the way, I've really been enjoying exploring the TanStack router codebase! My goal is to get more involved in open source to help maintain projects and learn from great engineering teams. Is there a process or pathway for becoming a member of the TanStack GitHub organization? I'd love to continue helping out where I can! |
Fixes a documentation issue where layout routes did not explicitly mention the requirement of an
<Outlet />component to render child routes.Summary by CodeRabbit
<Outlet />to render nested child routes.