Advanced
Kevin@olias
10/24/2023

Do you prefer one, two, or a combination? @kjs and I are designing a new TypeScript schema definition for Ponder to replace schema.graphql. This makes the TS lang server very snappy by eliminating a codegen step. Also unblocks direct database access.

In reply to @olias
max⚡️@maxp.eth
10/24/2023

Liking the zod vibes on the right 🤙

In reply to @olias
Kyle Scott@kjs
10/24/2023

One vote for the right!

In reply to @olias
Jeff Stout@stout
10/24/2023

Why not both? Named exports for the example on the left, and a default export for the right - have your cake and eat it too 🍰🍽️

In reply to @olias
10/24/2023

right side. Can you still `import type { Infer } ...` when using right side?

In reply to @olias
Peter Ferguson@peterferguson.eth
10/25/2023

Left seems similar to drizzle which I have been enjoying quite a lot recently so I side with that Would probably also prefer even more like drizzle where you point to the schema file and each named export defines a table schema

In reply to @olias
10/25/2023

Types as strings always felt like a failure to me, right seems like the way to go