switch function in drizzle
I'm following the "Add Clerk Authentication & Stripe Payments to your NextJS tRPC Application" tutorial. The tutorial uses T3 app + Prisma + Clerk.
I've used drizzle for my T3 app and need help converting this switch function written in Prisma-speak to Drizzle-speak....
Tanstack Table. flexRender
What is this flexRender? How can I use markup with him? How does it work? Is there any documentation about it?
drizzle
Just a heads up, if you are having issues using, run db:push and get these error messages, please try connecting to another network and do the push again, your provided ip might be blacklisted, or your isp might have them blacklisted:thinkies: , after connecting to my hotspot i was able to do the push and connect to drizzle studio without issues
Solution:
Just a heads up, if you are having issues using, run db:push and get these error messages, please try connecting to another network and do the push again, your provided ip might be blacklisted, or your isp might have them blacklisted:thinkies: , after connecting to my hotspot i was able to do the push and connect to drizzle studio without issues
t3 tRPC - CTX is undefined
Hey all. Finally checking t3 for the first time.
Question.
I was trying to add to the latest post query so that the latest post will be from the current user not all users....
Server side data fetching based on input from a client
So, I want to fetch data on the server with server components based on the input from the client component in this case
workspaceSlug. What is the best approach to go around this? I tried the pattern in this picture i havent got it to work
trpc useQuery/useMutation not inferring return type of prisma query
Env: Node18 , npm
i'm using turborepo with the server as Honojs + hono-trpc adapter and the client as react vite
So i've already did the setup as said in the docs and everything is working perfectly everything returned from the trpc procedures is inferred except when i return a prisma query then the inferred type is "any" ??
...
Solution:
i solved it
so it was an error with the context which contains (prisma and telegram bot) not being inferred from the client so i had to type it manually now all returned prisma queries works as expected...
