samuele Posts - Answer Overflow

samuele

Explore posts from servers

RRailway TtRPC TTCTheo's Typesafe Cult

Posts Comments

TTCTheo's Typesafe Cult

•Created by samuele on 9/1/2023 in #questions

broken dinamic page react quey

4 replies

TTCTheo's Typesafe Cult

•Created by samuele on 3/29/2023 in #questions

t3-turbo-clerk-drizzle

what about a stack for the edge? somebody has some example of this? it could be cool to use the zod types from the drizzle gen and implement them in the crud procedures on trpc

2 replies

TTCTheo's Typesafe Cult

•Created by samuele on 3/29/2023 in #questions

prisma latency on the edge

Hi guys, I saw the latest video from theo about the latency of using an orm like prima vs other types without the crap of query binding with rust ecc that slow down the performance. BUT in this case he talked about an edge runtime, what about a static region for the server and also for the DB? The req time would also be that slow?

23 replies

TTCTheo's Typesafe Cult

•Created by samuele on 2/23/2023 in #questions

E2E Tests t3-turbo stack

Hi guys I found out that in the community of the t3 stack, it’s common to use in the examples dirs the playwright for the e2e, but my question is... If I have a turbo repo with expo and nextjs with similar code... should I choose to test with cypress on both apps due to the lacking of playwright testing on iOS? or it’s enough to test it on the nextjs?

39 replies

TTCTheo's Typesafe Cult

•Created by samuele on 12/28/2022 in #questions

Angular - What about a t3 stack for the angular side

Don' be triggered by this post but... it would be cool to implement this type of “stack” not only for react (t3) and vue ecosystems (sidebase) but even for angular, and it could work! 🧐🧐 Maybe someday a lot of developers could have multiple choices using this type of stacks, even if they use different frameworks or libraries for the frontend side, to use most of the full type safe ecosystem

23 replies

TTCTheo's Typesafe Cult

•Created by samuele on 11/5/2022 in #questions

500 error on api call RAILWAY