You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Frontend routers are just now starting to become typesafe. That is, instead of just being able to <router-link> or router.push to just /any-old-string-path, they'll actually be aware of what routes you've defined and what URL params or hash values need to or could be there, and warn you if you try to do something different.
Not certain, but it seems like the tanstack router came up with the idea to do this first. Or at least they lit a fire under everyone, because React and Vue routers are looking into doing this now too. But I think tanstack might be more fully featured, and seems to be ready now.
You may notice... "first class search params". That is, it may obviate the need for our custom useParam composable. It seems like it has a ton of other useful features too.
Everything is working fine as it is right now, so this isn't 100% necessary. But it would be a nice long term improvement. I plan to start any new projects using tanstack router or equivalent (if React/Vue routers build things in as nicely as this one does).
The text was updated successfully, but these errors were encountered:
Frontend routers are just now starting to become typesafe. That is, instead of just being able to
<router-link>
orrouter.push
to just/any-old-string-path
, they'll actually be aware of what routes you've defined and what URL params or hash values need to or could be there, and warn you if you try to do something different.Not certain, but it seems like the tanstack router came up with the idea to do this first. Or at least they lit a fire under everyone, because React and Vue routers are looking into doing this now too. But I think tanstack might be more fully featured, and seems to be ready now.
https://tanstack.com/router/latest
https://router.vuejs.org/guide/advanced/typed-routes
You may notice... "first class search params". That is, it may obviate the need for our custom
useParam
composable. It seems like it has a ton of other useful features too.Everything is working fine as it is right now, so this isn't 100% necessary. But it would be a nice long term improvement. I plan to start any new projects using tanstack router or equivalent (if React/Vue routers build things in as nicely as this one does).
The text was updated successfully, but these errors were encountered: