Handling type inference and decoding in tRPC procedures can indeed be tricky, especially when dea...
Does anyone have any ideas on how I can avoid forcing the types in my tRPC procedure?
The reason I am doing this is cos a trpc
What I have done is forced the Encoded version in the input - This way the client is typed correctly. Inside the mutation callback, I simply force the type back to the decoded value.
This works, however, I am wondering if there is a nicer way to do this
Perhaps some function in schema that is well suited to this.
e
The reason I am doing this is cos a trpc
procedure.inputInputSchemaUtcBranded typesWhat I have done is forced the Encoded version in the input - This way the client is typed correctly. Inside the mutation callback, I simply force the type back to the decoded value.
This works, however, I am wondering if there is a nicer way to do this
Perhaps some function in schema that is well suited to this. e
Similar Threads
Was this page helpful?
