Cursor rule

1---
2description: How to implement tRPC endpoints
3alwaysApply: false
4---
5 
6TRPC has some specific syntax to follow for both frontend/client and backend/api:
7 
81. Client Example:
9 
10const trpc = useTRPC();
11const queryClient = useQueryClient();
12 
13// A readonly query
14const { data: tasks = [], isLoading, refetch } = useQuery(trpc.bullmq.listTasks.queryOptions({ limit: 50, offset: 0 }));
15 
16// A mutation
17const createMutation = useMutation({
18...trpc.tenants.create.mutationOptions(),
19onSuccess: () => {
20queryClient.invalidateQueries({ queryKey: trpc.tenants.list.queryKey() });
21}
22});
23 
24const createTenant = () => createMutation.mutate({ name: "New Tenant" });
25 
262. Backend Example:
27 
28   export const tenantsRouter = router({
29   list: publicProcedure
30   .output(z.array(TenantSchema))
31   .query(async () => {
32   return tenantsService.list();
33   }),
34 
35   create: publicProcedure
36   .input(z.object({ name: z.string().min(1) }))
37   .output(TenantSchema)
38   .mutation(async ({ input }) => {
39   const result = await tenantsService.create(input);
40   if (!result) throw new Error('Failed to create tenant');
41   return result;
42   }),
43   });
44 
453. (optional) A service file, not TRPC-specific, but separates more complicated database/etc
46   logic away from TRPC mechanics
47