Christopher Horobin

@y_nk @tannerlinsley @schanuelmiller @tan_stack @vite_js Yes satisfies keeps the inference but there are also context sensitive functions like `beforeLoad` return is piped into the parameter of `loader` which complicates things and also means the options have to be in a specific order

@c_horobin @tannerlinsley @schanuelmiller @tan_stack @vite_js most configs are provided usually with satisfies. wouldn't it be something which allows receiving the type of the route (since satisfies doesn't alter the type) _and_ provide typing built from parent too?

trying now to migrate from react-router to @tan_stack - i'm a bit confused as for why we need to have the path passed in `createFileRoute` since the routing is file-based 🤔 (cc @tannerlinsley)

@tannerlinsley @y_nk @schanuelmiller @tan_stack @vite_js We cannot use explicit types for the whole route definition because it needs to be an inference site. You need to infer from the route definition options users put there. I also prefer explicit types being totally optional for users and not required

@y_nk @schanuelmiller @tan_stack @vite_js While export type constraints are possible with some type gen, it’s not super resilient, and also wouldn’t work for none file-based routing configs either. cc @c_horobin

@y_nk @tannerlinsley @b_dammylolah @tan_stack This is a context sensitive function so the inference only works in a route definition. Seperate components would need explicit typing

@tannerlinsley @c_horobin @b_dammylolah @tan_stack i see. another choice would be to pass the `Route` object as 2nd arg of the component `(props, route) => JSX`? that'd mean props has to be passed as generic of the route tho. or maybe if so, add `route` to the props with a Props & { route: Route<Inferred> }` 🤔

Look how easy it is to protect my dashboard routes. Super clean, super Tanstack, no redirect new URL chaos, zero middleware.ts gymnastics. Not too much code. Readable. 😮‍💨 @tan_stack 😍

@tannerlinsley @y_nk @b_dammylolah @tan_stack You would still want to use Route bindings though. `Route.useX` and others which are extremely useful

@y_nk @b_dammylolah @tan_stack @c_horobin We do have an exponential compiler option to remove the first function call all together. No path. But it spooked people out.

@MrPotatoDip The array variant is a fun use of homomorphic mapped types

in tanstack start you can simply list a list safely with listOptions. Here is a route in array with params and search params both are typed.

@eliseumds @tannerlinsley @letstri @tan_stack Parsing string literal can be quick and not really a concern here. The challenge with route definitions is they infer from validators and return types. Using a schema validator with good TS perf helps a lot

@tannerlinsley @c_horobin @letstri @tan_stack From my exp, inference using template literal types is kinda slow (we have a ton of routes though). Have you noticed any perf impact in terms of type checking?

Is it even legal? I can fetch data in parent route and use it in any child routes. @tan_stack never ceases to amaze me

@eliseumds @tannerlinsley @letstri @tan_stack We basically generate a route tree which is easy for TypeScript to consume but nothing in the route definitions is precompiled. The point is that what you write is fully inferred. The route tree generation sprinkles explicit types to link routes together

@c_horobin @tannerlinsley @letstri @tan_stack From what I’ve seen, the pre-compiled routeTree.gen.ts contains the parent-child relationships and the path parameters are later inferred from the path strings. Is that it?

@eliseumds @tannerlinsley @letstri @tan_stack Just to clarify. This is not precompilation. The route tree generation just ties the routes together, the rest is inference.

@tannerlinsley @letstri @tan_stack How does that even work? Are the types pre-compiled?

@schanuelmiller @tannerlinsley `checkpoint` is like its way past my bedtime and really need to sleep and cannot put into words what I just did

@tannerlinsley and you are infecting @c_horobin with it...

If it wasn't clear before this already, I am 100% the most chaotic part of TanStack.

@colinhacks @schanuelmiller @tan_stack We have a fast path for empty objects because ` & {}` has a cost. Which for route parent merging happens in TSR. Might not for other libraries

@schanuelmiller @c_horobin @tan_stack ooo even fancier

this reminds me of what TanStack's "God of TypeScript" @c_horobin had implemented for @tan_stack Router #L61" target="_blank" rel="nofollow noopener">github.com/TanStack/route…

@seancassiere @tannerlinsley @lukerramsden Type level stuff is fun. The context switching between runtime and types can be challenging

@tannerlinsley @lukerramsden Also find yourself a @c_horobin

Discussing TypeScript APIs years ago (when I was a TS shunner): Smart person: "You should design your API for type-flow. Least context to most context". Me: "You're nuts. Dynamism is a feature" I now gratefully and happily eat those sad naive words every hour of every day.

Never thought I would see the day this type checks in less than a second 🤯

@GroveEsten @schanuelmiller @stevebeauge @someguys2nd @GabrielVergnaud Its likely not a bottleneck. It is best to trace before jumping to any conclusions. General advice like this can be useful but might not solve anything if the problem is something else

@c_horobin @schanuelmiller @stevebeauge @someguys2nd @GabrielVergnaud Meaning it was a common pattern for a large code base

Pro tip: Don't write your #TypeScript union types by hand, use a Type Catalog instead! Why are Type Catalogs better? Find out in the thread 🧵 👇

@schanuelmiller @stevebeauge @someguys2nd @GabrielVergnaud There are different considerations with larger types and it comes down to how the types are used but this example is quite small, its not going to be slow either way

@stevebeauge @someguys2nd @GabrielVergnaud it's subtle sometimes. paging @c_horobin

@codewithdavid Don't actually use prisma. I'm always scared to touch any orm.

@c_horobin You can fix Prisma 🙏

Never thought I would be described in this way. Genius I'd reserve for him. I just like types.

@schanuelmiller @mattpocockuk You mean this? #code/C4TwDgpgBAIhBmBDArgG2FAvFA3gKCingHtiAuKAZ2ACcBLAOwHMBuPAXzYgA8xiaMoSFAAKiGogC2lADwAVAMoRUEAMbAIAEwA0UOQDFUiJgD4suAlWVrgAfgoAKRmGTAKcJGmABKLGeQMANYMxADuDFA8GgyalHqGxlC2ekoq6lpQ7ggo6GzsUABkUADyYMB0xAzyqTZaugZGpmx4QtCl5ZXV1uk68Y1m2IrdGpqR3NGxuFAARuIU1PTMUOyWyThEjfZ9iUXTpCqIESuEFPiE5xvGWw07RIiolBCWhJx4eDx8AkQB6hUR8AEumkRvUEqYHMQypQtmIJNIgbVejdTN4KENgRkzlAAPTYu6BaB0SRgVCWGgQYDIGgRHD5RBxdGIvJvAEMBxYx7Axx0XyYMzs54zOZQADkJGIIuIlnY3m0llxUHpVFIESVAAN4I01VA6HEwOTHgxgHLCAq1YyetrdVAQhhGPAIDRyaNpiAoMAABbQcmU6nu8DQYjwKBqzk2bWHECSfgQE04vGMagQRCjOgYJCoB5C1SBd3EEMeHLAbWWTXGCgZx4cbxsIA" target="_blank" rel="nofollow noopener">typescriptlang.org/play/?#code/C4…

How can I conditionally add a property to a type based on another property? Type inference fails as soon as `flag` is present: tsplay.dev/NDQjVm @mattpocockuk

Type level code is just another language to learn. If you're uncomfortable looking at it, you probably don't know it that well

It's like stale vs fresh

Inference still happens, even during generation. You still wait for it.