tkdodo.eu
⚛️ Maintaining TanStack Query
🔮 https://query.gg
👨💻 Software Engineer @sentry.io
📚 Blog at https://tkdodo.eu
🇦🇹 Vienna, Austria
👧👦 Father of two
940 posts
7,182 followers
340 following
Regular Contributor
Active Commenter
comment in response to
post
Probably @tannerlinsley.com said that 😄
comment in response to
post
Then you'll just tell me all about it next time we meet 🙌
comment in response to
post
Love the slide 😂. Is there a recording of the talk 👀 ?
comment in response to
post
Loved our discussion today - your feedback is always appreciated 🙏
comment in response to
post
But design decisions usually can only be changed between majors.
comment in response to
post
This is the reality of feedback in open source. Now lots of people are not like this, and kind feedback is always welcome. But please also understand that feedback is most valuable before a major version hits "stable". Because then, reported issues can still be addressed. Bugs can always be fixed...
comment in response to
post
isn't like they expect it to be, so they open an issue, very often in a rude tone à la "which clown thought of this API? This is totally messed up" or "Here's a list of principles you're violating with this, no one in their right mind would do that!"
comment in response to
post
they instantly upgrade. Sorry to break it to you too but if no one provides feedback, the beta version is exactly the same as the "stable" one. It doesn't have less bugs, it's not more "battle tested", nothing. It doesn't age like wine.
So now they use it or upgrade and see that something...
comment in response to
post
Every time we release a beta or RC version, we get a good amount of comments like "when is it finally stable?" and "I can't wait to be finally able to start using it". As if people are really waiting for a new major to drop without even looking at the RC. Then, on the first day of the major...
comment in response to
post
This is not what I was wanting to say at all, sorry if that's how it came across. It definitely helps to see and understand the other side a bit. Most open source developers I know are product engineers themselves- me included. So please, I know how the game works. Where I'm coming from is this:
comment in response to
post
sorry but I don't understand users who wait forever until the V1 is *finally* ready (why did it take you so long??) and _then_ complain about API design decisions 🤷♂️
if you CARE and want to be heard, try out the beta. If not, accept what others have come up with...
comment in response to
post
Awesome, looking forward to meeting you in person 🙌
comment in response to
post
When you use more complex types, adding return types becomes hard and it's better to use inference. For simple types, I doubt that it matters much.
comment in response to
post
how about:
import { defaultQueryFn } from '@tanstack/react-query'
useQuery({
queryKey,
queryFn: defaultQueryFn<MyType>()
})
?
comment in response to
post
Yes 😂
comment in response to
post
This has been by far the most requested RTKQ feature for years, and I'm extremely happy to finally have first-class support for this use case!
Huge thanks to @tkdodo.eu for encouraging us to use React Query's API design and implementation approach, and offering his advice on building it!
comment in response to
post
"Depends"
comment in response to
post
infer all the things 😂
comment in response to
post
Yes, and it's specific to nextJs. It's fine with server functions in @tanstack.com start.
comment in response to
post
So, in short, there is no simple way to do it 😅?
comment in response to
post
No, that's what I want the helper type for 😅
comment in response to
post
also works with Omit<T, never> 😅
comment in response to
post
okay wtf that works - but WHY ?
www.typescriptlang.org/play/#code/M...
comment in response to
post
nope, same result: www.typescriptlang.org/play/#code/M...
comment in response to
post
seems like it, but also 🤯
comment in response to
post
no, same result: www.typescriptlang.org/play/#code/M...
comment in response to
post
I remember upgrading webpack from v2 -> v3 a long time ago, which took me over a week. It was a hot mess 😂
The next project we started with CRA and it was perfect until ejecting was needed.
These days, vite is really all you need to get going. Way better than hundreds of lines of webpack config 😅
comment in response to
post
Also wild that create-tanstack-app was already taken on npm 😔
comment in response to
post
It's just too long for a bsky post
comment in response to
post
comment in response to
post
That also means I don't know where it should go in the docs because we don't have nextJs specific docs (yet...)