DogPawHat

@dogpawhat.tech

"The core problem is that JavaScript isn’t real." https://dogpawhat.tech/

So I do have a PR i need to update on router for its docs, but I also need to update the examples. ...which means updating query to 5.102 on those. ...which I can't do without violating the 24 minimum release age policy 🤣

DogPawHat@dogpawhat.tech · 3d ago

I updated the v5 migration guide with the full details. Rest of TanStack Query's docs related to prefetching and framework integration use the new methods. a quick read should give you all you need. tanstack.com/query/latest...

Quick TLDR thread of Unified Imperative Query Methods - Query had 6 methods for impertifly fetching query data, 3 each for standard and infinite query - those methods are deprecated now in favor of just `client.query` and `client.infiniteQuery`

Dominik 🔮@tkdodo.eu · 3d ago

Welcome, TanStack Query v5.102.0 🎉 Biggest release since v5 is now out the door. We usually ship often (as you can see by the 3 digit minor number), but I've also never had a full week to work nonstop on OSS. 🐞 27 bugfixes ⚡ 4 perf improvements 🔥 1 feature - Unified Imperative Query Methods

Thanks to all contributors of this release. Special shoutout to @dogpawhat.tech, who started working on implementing the RFC of Unified Imperative Query Methods ... checks notes ... November last year 😂. We went back and forth a lot and I changed my mind midway too. Hope we got it right 🤞

RFC: Unified Imperative Query Methods · TanStack query · Discussion #9135

Context Sometimes, APIs don’t evolve well. I’ve seen the situation a couple of times that we add an API, and we think it’s great, and then after some time, we add another API that does something si...

github.com

My personal projects: "Hmm, maybe if I switch from Biome to Oxlint, I could shave 420 femtoseconds off each CI run and make AI work faster?" At work: Today I had to convince a team member that having over 500 ESLint/TypeScript errors and no CI is, in fact, not a good idea. I just can't 🫠

A screenshot from Microsoft Teams message:

We are dependent on a foundation for the rest of the team to move forward with features, and what you’re describing boils down to linting and tests.
[redacted]
Do you prefer to move forward with the tasks and unblock everyone else's work, even if it’s not 100% perfect yet, and improve it later? Or would you rather have everyone wait and everything be blocked because of you?
 
It’s a matter of choice, we aren't working alone.

I'm beginning to think any new software offering with the pitch of "replacing legacy spreadsheet systems" is the hight of hubris. If you come at King Excel you best not miss.

Software is the only industry where you can plan to climb the Devil's Ladder on Carrauntoohil and realise a week from the deadline your actually climbing Everest.