tRPC is butchering object types in return types

So if I have a mutation that returns this type

{ name?: string }

{ name?: string }

the type that tRPC infers for the mutation is

type R = ReturnType<typeof trpcClient.mut.mutate>
R = Promise<Record<"name", string | undefined>>

type R = ReturnType<typeof trpcClient.mut.mutate>
R = Promise<Record<"name", string | undefined>>

This is not the same, with exactOptionalPropertyTypes.

Anyone familiar with this who can provide some info about it?

tRPC•3y ago•

5 replies

tRPC is butchering object types in return types

So if I have a mutation that returns this type

{ name?: string }

{ name?: string }

the type that tRPC infers for the mutation is

type R = ReturnType<typeof trpcClient.mut.mutate>
R = Promise<Record<"name", string | undefined>>

type R = ReturnType<typeof trpcClient.mut.mutate>
R = Promise<Record<"name", string | undefined>>

This is not the same, with exactOptionalPropertyTypes.

Anyone familiar with this who can provide some info about it?

Join the Discord to ask follow-up questions and connect with the community

Move Fast & Break Nothing. End-to-end typesafe APIs made easy.

4,951 Members