3 ms·
Have you checked out https://kirimase.dev https://kirimase.dev?
by cjr 3y ago
Have you checked out https://kirimase.dev https://kirimase.dev?
- petesergeant 3y agoThis looks excellent, thank you. I'm iterating a lot of startups at the moment, and sort of home-growing a framework, but each new product I want to replace bits of it with off-the-shelf tooling, and this is an excellent selection of components.
- erhaetherth 3y agoNo, hadn't heard of that. Looks like it's doing a bit too much. I'm not sold on ORMs or auto-genned scaffolding apps. The tRPC lib they're using OTOH looks interesting. Kind of. Looks like I'd have to give up my server lib/router for theirs, but then it looks like they botched the client-side error formatting which is the one thing I haven't solved: https://trpc.io/docs/server/error-formatting https://trpc.io/docs/server/error-formatting How is this good UX? <pre>Error: {JSON.stringify(mutation.error.data.zodError, null, 2)}</pre> Formik (https://formik.org/docs/api/errormessage https://formik.org/docs/api/errormessage) does OK with the "touched" and "errors" objects, that helps you render out the error messages nicely, next to the inputs, but for my very first use-case I wanted to validate a File input and it seems to struggle with that a bit. Can't do it without suppressing some TS errors but maybe it's an edge case. And it of course doesn't handle the server half of the equation. So.. yeah.