trpc-conventions

tRPC router conventions establish a standardized structure for building API endpoints with consistent input validation via Zod, protected procedures, error handling using TRPCError codes, and pagination. This ensures maintainable CRUD-like operations across your backend.

Use protectedProcedure for routes requiring authentication and handle errors with TRPCError using specific codes like NOT_FOUND, UNAUTHORIZED, FORBIDDEN, and BAD_REQUEST. This pattern ensures consistent error responses and enforces access control across all endpoints.

Define tRPC procedures with Zod schemas for input validation, then execute drizzle-orm database queries within the procedure logic. Chain validation and database operations to ensure type-safe, validated data flow from client to database.

Yes. Call tRPC routers from React components using the api hooks, implementing pagination through limit and offset parameters. This provides type-safe, end-to-end integration with consistent client usage patterns.

Apply TRPCError codes including NOT_FOUND for missing resources, UNAUTHORIZED for missing credentials, FORBIDDEN for insufficient permissions, and BAD_REQUEST for invalid input. These standardized codes enable predictable client-side error handling.

Router conventions reduce maintenance overhead and inconsistency when creating features-related routes for list, getById, create, update, and delete operations. Standardization ensures all endpoints follow the same validation, error handling, and export patterns.