No description
- Rust 100%
Owen Phillips
b56be8ce5a
Link must be a descendant of Router. The nav was previously rendered as a sibling of Router::<Route> in App, so the server-side render panicked with \"Link must have access to a parent router\" on every page load. Fix: added a Layout component (#[layout(Layout)] in the Route enum) that renders the nav + Outlet::<Route>. All routes now inherit the router context and Links resolve correctly. Tested: cargo check --features server and cargo check --features web --target wasm32-unknown-unknown both pass cleanly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| migrations | ||
| src | ||
| .env.example | ||
| .gitignore | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| Dioxus.toml | ||
| LICENSE | ||
| PLAN.md | ||
| README.md | ||