Router Adapters

Router adapters are implemented as templates with a small hook interface. The generator calls these hooks to produce files, names, imports, and procedure code.

Generic template interface (example):

interface RouterTemplateHooks<Table = any> {
  filePath(
    table: Table,
    ctx: {
      outDir: string;
      naming?: { routerSuffix?: string; procedureCase?: 'camel' | 'kebab' | 'snake' };
    }
  ): string;
  routerName(
    table: Table,
    ctx: { naming?: { routerSuffix?: string; procedureCase?: 'camel' | 'kebab' | 'snake' } }
  ): string;
  procedures(table: Table): Array<{ name: string; varName: string; code: string }>;
  imports?(tables: Table[], ctx?: any): string;
  prelude?(tables: Table[], ctx?: any): string;
  header?(table: Table): string;
}

• filePath: absolute path for a table’s router file
• routerName: the exported constant name
• procedures: an array of procedures; each item provides an exported key (name), a variable identifier (varName), and the implementation code
• imports: additional imports at file top
• prelude: helper code after imports
• header: banner/comment string at top

Example custom template: see /templates/custom

Notes:

• Validation libraries can be reused/injected by the generator (Zod/Valibot/ArkType)
• Output typing is attached by the generator when possible
• Adapters can map to oRPC, tRPC, Express handlers, etc., by changing the procedures implementation