Inferencia de Tipos
Esta página fue traducida por PageTurner AI (beta). No está respaldada oficialmente por el proyecto. ¿Encontraste un error? Reportar problema →
A menudo es útil acceder a los tipos de tu API desde tus clientes. Para este propósito, puedes inferir los tipos contenidos en tu AppRouter.
@trpc/server exporta los siguientes tipos auxiliares para ayudar a inferir estos tipos desde el AppRouter exportado por tu enrutador @trpc/server:
-
inferRouterInputs<TRouter> -
inferRouterOutputs<TRouter> -
inferProcedureInput<TProcedure> -
inferProcedureOutput<TProcedure> -
inferSubscriptionInput<TProcedure> -
inferSubscriptionOutput<TProcedure>
Inferencia de Tipos de Entrada y Salida
Supongamos que tenemos este enrutador de ejemplo:
server.tstsimport {initTRPC } from '@trpc/server';import {z } from "zod";constt =initTRPC .create ();constappRouter =t .router ({post :t .router ({list :t .procedure .query (() => {// imaginary db callreturn [{id : 1,title : 'tRPC is the best!' }];}),byId :t .procedure .input (z .string ()).query ((opts ) => {// imaginary db callreturn {id : 1,title : 'tRPC is the best!' };}),create :t .procedure .input (z .object ({title :z .string (),text :z .string (), })).mutation ((opts ) => {// imaginary db callreturn {id : 1, ...opts .input };}),onPostAdd :t .procedure .input (z .object ({authorId :z .string () })).subscription (async function* ({input }) {// imaginary event sourceyield {id : 1,title : 'tRPC is the best!',authorId :input .authorId ,};}),}),});export typeAppRouter = typeofappRouter ;
server.tstsimport {initTRPC } from '@trpc/server';import {z } from "zod";constt =initTRPC .create ();constappRouter =t .router ({post :t .router ({list :t .procedure .query (() => {// imaginary db callreturn [{id : 1,title : 'tRPC is the best!' }];}),byId :t .procedure .input (z .string ()).query ((opts ) => {// imaginary db callreturn {id : 1,title : 'tRPC is the best!' };}),create :t .procedure .input (z .object ({title :z .string (),text :z .string (), })).mutation ((opts ) => {// imaginary db callreturn {id : 1, ...opts .input };}),onPostAdd :t .procedure .input (z .object ({authorId :z .string () })).subscription (async function* ({input }) {// imaginary event sourceyield {id : 1,title : 'tRPC is the best!',authorId :input .authorId ,};}),}),});export typeAppRouter = typeofappRouter ;
Usando los helpers, podemos inferir los tipos de nuestro enrutador. El siguiente ejemplo muestra cómo inferir los tipos del procedimiento post.create:
client.tstsimport type { inferRouterInputs, inferRouterOutputs } from '@trpc/server';import type { AppRouter } from './server';type RouterInput = inferRouterInputs<AppRouter>;typeRouterOutput = inferRouterOutputs<AppRouter>; typePostCreateInput = RouterInput['post']['create']; typePostCreateOutput = RouterOutput['post']['create'];
client.tstsimport type { inferRouterInputs, inferRouterOutputs } from '@trpc/server';import type { AppRouter } from './server';type RouterInput = inferRouterInputs<AppRouter>;typeRouterOutput = inferRouterOutputs<AppRouter>; typePostCreateInput = RouterInput['post']['create']; typePostCreateOutput = RouterOutput['post']['create'];
Inferencia de Tipos de Procedimientos Individuales
Si ya tienes acceso a un procedimiento específico en tu enrutador, puedes inferir su entrada o salida directamente:
client.tstsimport type {in ferProcedureInput,inferProcedur eOutput,} from '@trpc/server';importtype { AppRouter } from './server'; typePostByIdInput = inferProcedureInput<AppRouter['post']['byId']>; typePostByIdOutput = inferProcedureOutput<AppRouter['post']['byId']>;
client.tstsimport type {in ferProcedureInput,inferProcedur eOutput,} from '@trpc/server';importtype { AppRouter } from './server'; typePostByIdInput = inferProcedureInput<AppRouter['post']['byId']>; typePostByIdOutput = inferProcedureOutput<AppRouter['post']['byId']>;
Para suscripciones, puedes inferir la entrada de la suscripción y el tipo de dato emitido:
client.tstsimport type {in ferSubscriptionInput,inferSubsc riptionOutput,} from '@trpc/server';importtype { AppRouter } from './server'; typeOnPostAddInput = inferSubscriptionInput<AppRouter['post']['onPostAdd']>; typeOnPostAddOutput = inferSubscriptionOutput<AppRouter['post']['onPostAdd']>;
client.tstsimport type {in ferSubscriptionInput,inferSubsc riptionOutput,} from '@trpc/server';importtype { AppRouter } from './server'; typeOnPostAddInput = inferSubscriptionInput<AppRouter['post']['onPostAdd']>; typeOnPostAddOutput = inferSubscriptionOutput<AppRouter['post']['onPostAdd']>;
Inferir tipos de TRPCClientError
También es útil inferir el tipo de error para tu AppRouter
client.tstsimport { TRPCClientError } from '@trpc/client';import type { AppRouter } from './server';import{ trpc } from './trpc'; exportfunction isTRPCClientError( cause: unknown,): cause isTRPCClientError<AppRouter> { return cause instanceof TRPCClientError; }async function main() {try {await trpc.post.byId.query('1');}catch (cause) { if (isTRPCClientError(cause)) { // `cause` is now typed as your router's `TRPCClientError` console.log('data', cause.data);} else {// [...]}}}main();
client.tstsimport { TRPCClientError } from '@trpc/client';import type { AppRouter } from './server';import{ trpc } from './trpc'; exportfunction isTRPCClientError( cause: unknown,): cause isTRPCClientError<AppRouter> { return cause instanceof TRPCClientError; }async function main() {try {await trpc.post.byId.query('1');}catch (cause) { if (isTRPCClientError(cause)) { // `cause` is now typed as your router's `TRPCClientError` console.log('data', cause.data);} else {// [...]}}}main();