Itspatricku
@itspatricku.bsky.social
I always split router/page logic from my actual features. This made migrating from remix (spa) to @tanstack.com router a breeze. A lot less non null assertions 🙈🙈
January 5, 2025 at 10:55 PM
I always split router/page logic from my actual features. This made migrating from remix (spa) to @tanstack.com router a breeze. A lot less non null assertions 🙈🙈
You mean something like this, hey? Agreed, it’s a solid solution and probably what I will use.
Tbf, what I m looking for is achievable with just tanstack router loader. It would just feel ✨ delightful ✨declaring the query once and using its results across loader and component.
Tbf, what I m looking for is achievable with just tanstack router loader. It would just feel ✨ delightful ✨declaring the query once and using its results across loader and component.
January 5, 2025 at 4:23 PM
You mean something like this, hey? Agreed, it’s a solid solution and probably what I will use.
Tbf, what I m looking for is achievable with just tanstack router loader. It would just feel ✨ delightful ✨declaring the query once and using its results across loader and component.
Tbf, what I m looking for is achievable with just tanstack router loader. It would just feel ✨ delightful ✨declaring the query once and using its results across loader and component.
@tkdodo.eu @tannerlinsley.com hear me out… one thing I don’t “love” is that I need to call postQueryOptions(postId) twice. It’s fine - It makes sense, but I wished I could just “reuse” the same call. Maybe this is crazy, but do you think an API like this be possible? In query+router?
January 5, 2025 at 3:00 AM
@tkdodo.eu @tannerlinsley.com hear me out… one thing I don’t “love” is that I need to call postQueryOptions(postId) twice. It’s fine - It makes sense, but I wished I could just “reuse” the same call. Maybe this is crazy, but do you think an API like this be possible? In query+router?