Describe the bug
When using the component, the search prop is pulling the wrong types.
Instead of inferring the types for the search query parameter based on the route, it instead is pulling out the path params from the global context.
This bug is present only at the type-level, the actual runtime code works just fine.
Your Example Website or App
https://stackblitz.com/edit/tanstack-router-3uax76?file=src%2Fmain.tsx
Steps to Reproduce the Bug or Issue
- Go to the Stackblitz example.
- View lines 424 - 432.
Expected behavior
As a user, I expect to get the Typescript typings on the search prop for the route I'm going to.
Screenshots or Videos
Platform
- OS: macOS
- Browser: Chrome
- Version: 116
Additional context
Using 0.0.1-beta.190.