T
tRPC

best practices for organizing routes/procedures?

best practices for organizing routes/procedures?

Jjack
View on Discord
2/11/2023
i'm trying to find some practices/styles in which people generally define routes with trpc. currently im just doing a router per data entity, and defining crud operations on there, but there's a lot of caveats that are kind of defined with REST, that i'm unsure of how to handle here. one idea i had was to define my router as such: (assume each subrouter will have routes) 
export const selectionRouter = createTRPCRouter({
  // CREATE
  create: createTRPCRouter({}),
  // READ
  read: createTRPCRouter({
    getAllValidSelections: publicProcedure.query(async ({ ctx }) => {...}),
  }),
  // UDPATE
  update: createTRPCRouter({
    editSelections: protectedProcedure.mutation(async ({ ctx, input }) => {...}),
  }),
  // DELETE
  delete: createTRPCRouter({}),
});
export const selectionRouter = createTRPCRouter({
  // CREATE
  create: createTRPCRouter({}),
  // READ
  read: createTRPCRouter({
    getAllValidSelections: publicProcedure.query(async ({ ctx }) => {...}),
  }),
  // UDPATE
  update: createTRPCRouter({
    editSelections: protectedProcedure.mutation(async ({ ctx, input }) => {...}),
  }),
  // DELETE
  delete: createTRPCRouter({}),
});
another thing is reusing logic- i have a getSelectionsById, and a getOwnSelections. of course, these are gonna have a lot overlap because its entirely the same logic, but in one i'm passing conditional ids, and in the other im passing the session id. of course i could extract this out, but it feels inconsistent with the rest of the logic living inside of the router. i'm sure there's no clear cut answer for most of this, but i was just wondering how people generally go about this, or if there are any guides or blogs about this topic.
Nnlucas
View on Discord
2/11/2023
Most of what you've learned in REST-land does transfer over. Routers for entities is a just a sane way to structure your code, but it's a little more natural to have a procedural function Context and Middlewares can inject services/invert-control, so the DI techniques you may have learned with Controllers can also be adapted If you have a lot of similar CRUD routers you can also use factories to create those routes with a little configuration - I do this a lot

Looking for more? Join the community!

T
tRPC

best practices for organizing routes/procedures?

Join Server
Recommended Posts
Validating input inside middleware declaration```js const enforceUserIsCreatorOfEvent = t.middleware(({ ctx, next, input }) => { if (!input.evenFetch errors on stale pagesRecently I have been getting a lot of fetch errors on stale pages, in particular ones that have querDistribute typesafe tRPC Client in an NPM libraryHi ! super fan of trpc over here. We are building a javascript sdk for our API that is essentiallyMutation or query for something that updates db, but runs on every app load?I have 2 operations that need to run before showing my app UI. Those operations perform updates in DWebsocket is not defined errorI'm getting a "WebSocket is not defined error" on my next app connected to an express backend. Any i@trpc/server in a non-server environment Error in Azure CIIm trying to add vitest unit tests for my trpc procedures. I followed some examples and on the localHow are people handling authorization?I noticed that with V10, any mentions of `trpc-shield` are gone from the documentation. Also, it onlVitest context router callerHi, Im trying to setup vitest to test trpc. I would like to have a trpc approuter caller to be acces