T
tRPC

How does routing work in tRPC especially when using merged routers?

How does routing work in tRPC especially when using merged routers?

Rrockchalkwushock
View on Discord
4/21/2023
I am having trouble understanding how tRPC lays out routes. Let's say I have the below 
export const apiRouter = router({
  version: publicProcedure.query(() => {
    return { version: '0.42.0' }
  }),
  hello: publicProcedure
    .input(z.object({ username: z.string().nullish() }).nullish())
    .query(({ input, ctx }) => {
      return {
        text: `hello ${input?.username ?? ctx.user?.name ?? 'world'}`,
      }
    }),
})

export const appRouter = router({
  api: apiRouter,
  // ...other routers
})

// server.ts
server.register(fastifyTRPCPlugin, {
  prefix: '/trpc',
  trpcOptions: { router: appRouter, createContext },
})
export const apiRouter = router({
  version: publicProcedure.query(() => {
    return { version: '0.42.0' }
  }),
  hello: publicProcedure
    .input(z.object({ username: z.string().nullish() }).nullish())
    .query(({ input, ctx }) => {
      return {
        text: `hello ${input?.username ?? ctx.user?.name ?? 'world'}`,
      }
    }),
})

export const appRouter = router({
  api: apiRouter,
  // ...other routers
})

// server.ts
server.register(fastifyTRPCPlugin, {
  prefix: '/trpc',
  trpcOptions: { router: appRouter, createContext },
})
My assumption is that from the above example I have: 
GET /trpc/api/version
GET /trpc/api/hello?username=Bob
GET /trpc/api/version
GET /trpc/api/hello?username=Bob
However when using Insomnia to query the endpoints as I familiarize myself with tRPC more I get 404s. Could someone explain this to me better? I am running: 
@trpc/server 10.21.0
pnpm 8.2.0
node 18.15.0
@trpc/server 10.21.0
pnpm 8.2.0
node 18.15.0
LLonghumans
View on Discord
4/21/2023
In Postman I had to use: GET /trpc/user.getUsers So in your case it would be: GET /trpc/api.version Also new to TRPC and unfamiliar with Insomnia, but I hope that helps.
Rrockchalkwushock
View on Discord
4/21/2023
@Longhumans you sir are a fucking boss! Thank you I would never have figured that out. Makes some sense now with the way the client consumes: trpc.api.version.query() Thanks again!
LLonghumans
View on Discord
4/25/2023
Happy it helped 🙂

Looking for more? Join the community!

T
tRPC

How does routing work in tRPC especially when using merged routers?

Join Server
Recommended Posts
where is useQuery [key]?Learning trpc, i use to tanstack with queryKey, can not find how that works with trpc, if i want tuseInfinieQuery with initialData, Refetch only after second change of inputsHi everyone, I have the problem as stated in the title. My code looks like the following: ```ts Adding tRPC HOC breaks zustandIt seems that adding the trpc hoc breaks my zustand stores initial values and generates bad data. AfNext.js + tRPC, multitenancy, access Next.js Router when setting tRPC headersHey all! I'm writing a multi-tenant solution. Most Next.js pages lie under the `/pages/[tenantKey]/`getInfiniteData returns undefinedI am using the t3-stack. Whenever I am calling getInfiniteData it returns undefined. ``` console.loEnable both `useQuery` and a raw `query` from the frontend (for use in async validation)Hello everyone, some context: ``` . I'm building a project with a variant of the t3 stack (key pointNextjs http endpoint (no prisma)I have simple pages/api/todoEndpint how do i call this endpoint with trcp? I don't want to use prismAdding clerk auth object to createServerSideHelpersSo I followed clerk's docs for TRPC (https://clerk.com/docs/nextjs/trpc) and I added `auth` to the `