fix(router): relative links with index routes #25309
Merged
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.
Why
Fix #25282
How
When doing relative navigation we need to track if we are travelling from a index route or not. This issue is a slight regression, as we used to handle this in some scenarios, but this fix should handle it in all. I've added additional metadata to the
routeInfo
to track is the current route is an index route.Test Plan
Tested repo in issue. Added scenario to navigation tests
Checklist
npx expo prebuild
& EAS Build (eg: updated a module plugin).