feat(router): allow type-safe hooks to access ancestor route data#53
Merged
feat(router): allow type-safe hooks to access ancestor route data#53
Conversation
Add parent reference chain to RouteContextValue, enabling useRouteParams, useRouteState, and useRouteData to access data from ancestor routes in nested route hierarchies. Changes: - Add `parent` field to RouteContextValue for traversing route hierarchy - Add `findRouteContextById` helper to search ancestor chain - Create shared `useRouteContext` internal hook to reduce duplication - Update hooks to traverse parent chain when looking for route by ID - Update error messages from "mismatch" to "not found in hierarchy" - Add tests for nested route access scenarios - Update documentation to reflect new capability Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
useRouteParams,useRouteState, anduseRouteDatato access data from ancestor routes in nested route hierarchiesRouteContextValuefor traversing route hierarchyuseRouteContextinternal hook to reduce code duplicationProblem
When using nested routes like:
Inside the
admin.userpage component, callinguseRouteState(adminRoute)would throw an error because the hooks only checked the nearestRouteContextand threw if the ID didn't match.Solution
Added a
parentfield toRouteContextValuethat references the parent route's context. Hooks now traverse this chain to find the route with the matching ID.Test plan
🤖 Generated with Claude Code