useMatches and UseRouterStateResult.matches are always any[]. Why isn't this typed? Is this expected? #3165
Unanswered
doyoueventruck
asked this question in
Q&A
Replies: 1 comment
-
can you please provide a complete minimal example by forking one of the existing examples on stackblitz? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using file-based routing, and I've registered the router instance for type safety.
useMatches
andUseRouterStateResult.matches
are always any[]. Why isn't this typed? Is this expected?ParseRoute<typeof routeTree>
is always any also, which is driving the any[] result of matches I imagine.As an aside, it would be really nice to have a hook / convenient way to retrieve the current route / route match.
Thanks much! Love the library (other than this frustration) so far 😄
Beta Was this translation helpful? Give feedback.
All reactions