🤯 tRPC 10 enables VS Code's "Change All Occurrences" feature to work _across the client/server boundary_!
In this video, I rename a procedure input using "Change All Occurrences", and that change propagates to anywhere the input is used across the entire app. 🤩
cc
Conversation
One Dark Pro Monokai Darker with the Hasklig font
3
This brings up the controversial question of using IDE superpowers to compensate for architecture limitations. The power is alluring, but does it scale across team-members?
1
1
I can't argue with this line of questioning. In my case, it's just me so I can get away with it. 🤓
1
4
Show replies
Curious about how the organisation model in the Prisms schema. Do you scope everything under the organisation ?
1
I’m not here to talk about the internal code that I probably shouldn’t be sharing publicly 😅
(Don’t look 🫣)
Look! Shiny tRPC VS Code rename features!
1
1
Show replies
tRPC’s end to end type checking really only works in a monorepo/single code base. That’s what I have.
1
2
Show replies
Won't this cause a production outage?
Local code changes may be atomic and eveb cross service boundaries, but deploys to production (updating the live server and client processes) are not.
The new client needs to stay compatible with the old server, and vice versa...
2
2
Thats nice if you have 1-1 relationship and its open in IDE. What if we have 500+ microservices? :D
1
Discover more
Sourced from across Twitter
Uh oh. Is "MagSafe is actually bad" the next "tabs vs spaces" or "let vs const" tech debate?
It is that time of the week for one to start up...
Quote Tweet
I will never use one of these hellish cables to charge my Mac. I’m on my 2nd MagSafe-ready machine and have still only charged with USB-C twitter.com/adamrackis/sta…
Show this thread
6
24
This is among the weirdest date inputs I've ever seen.
read image description
ALT
1
2