A place for developers to talk about building on Farcaster.

/dev

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.

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

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

Making investing together better https://forumdaos.com | Variant Founder Fellow | Cambridge Alum | Formerly Ireland's #3 powerlifter (74kg)

Agree, one named export per table would be cleaner.

The reason we're considering this `schema` object, which isn't clear from the screenshot, is that the references (foreign key column names, enum names) have type-level validation and intellisense hints. That's not possible if each table is an isolated named export.