Spaceman
Spaceman
TTCTheo's Typesafe Cult
Created by shikishikichangchang on 3/23/2024 in #questions
retry logic with server action
Honestly if you need to retry, I would use something like https://www.npmjs.com/package/swr which has polling and then put your logic into a api endpoint. I think retrying is sort of outside the behavior scope for a form submit.
3 replies
TTCTheo's Typesafe Cult
Created by Spaceman on 7/28/2023 in #questions
Pattern for Next.js path strings (App Router)
8 replies
TTCTheo's Typesafe Cult
Created by Spaceman on 7/28/2023 in #questions
Pattern for Next.js path strings (App Router)
Thanks for this! This led me down a rabit hole and I also found this solution which is a bit less typesafe but seems a bit more plug and play: https://github.com/tatethurston/nextjs-routes Still deciding on which one to go with.
8 replies
TTCTheo's Typesafe Cult
Created by ACPixel on 4/25/2023 in #questions
PlanetScale deployments when using T3, prisma, and vercel
I'm also trying to figure this out
5 replies
TTCTheo's Typesafe Cult
Created by Michael Schaufelberger on 5/13/2023 in #questions
Alternative to Planetscale for multiple smaller apps
https://neon.tech/ has branching. I think its cooler than what planetscale has, but I havent built anything in production on it.
4 replies
TTCTheo's Typesafe Cult
Created by shikishikichangchang on 4/15/2023 in #questions
Ideal UI behaviour for tables on mobile
I think there are 2 ways of doing things. 1. Table on larger screens and card and stacked data in smaller screens - One non-react example of this is something like https://johnpolacek.github.io/stacktable.js/ . I've never found a react based lib for this that I like but you can mimic the behavior with tailwind. 2. X Scrolling - You can just let the table have x direction scrolling as the screen gets smaller. I went into great effort to try to do a hybrid of these for a project where we had kind of line item elements with cells in the left-most 50% of the table and so I just broke the row in half and stacked both halves as the screen got smaller. That was ok but it turned out to be a bit of a bitch to implement. Next time I'll just go with side scrolling and a typical table component with tailwind.
10 replies