Chapter 1) The Router API

[KATT]

The router API

Challenges with the current implementation

• TypeScript performance. Each procedure added creates a new Router that TypeScript chokes on as the underlying complexity grows non-linearly with each added procedure - each procedure basically has its "own instance" within the compiler even if it's flattened and unaffected at runtime.
• I find that those queries are hard/unintuitive to write, I find myself counting parentheses and curly brackets all too often. Arguably, your suggestions with the resolver API could also address this.
• No CMD+click

Suggested implementation

• Flat router
• No automatic prefixing (breaks jump to definition / CMD+click)

import { z } from 'zod';
import { initTRPC } from './trpc/server';

const trpc = initTRPC<Context>();

const postRouter = trpc.router({
  queries: {
    postById: null as any /* resolver implementation is a separate discussion */
    postAll: null as any /* resolver implementation is a separate discussion */
  },
  mutations: {
   postAdd: null as any /* resolver implementation is a separate discussion */
});

const userRouter = trpc.router({
  queries: {
    userAll: null as any /* resolver implementation is a separate discussion */
  },
);

const appRouter = trpc.mergeRouters(
  postRouter, 
  userRouter, 
  // ...
)

[KATT]

Closed by #33