NerrorFormatter, though it works a little differently than you suggest
NI think you need to have a read of the docs page, you shouldn't be throwing any new error in there
NMaybe it's possible but I wouldn't expect to be able to manipulate the HTTP content in an RPC framework
NYou need to let tRPC do its thing and handle errors in javascript via the client
NYou can throw a TRPCError in your own code with a relevant error code
NYou might be able to use a middleware to catch your own base-class and re-emit as a TRPCError
NDo let me know if it works. I think it should be not 100% sure
NWe're talking about improved docs right now and I would make sure this goes in
NMakes sense, middleware order usually matters
NThanks for that, looks an essential pattern for us to document
NI always do it but I believe it’s optional, you can swap/extend the context using middlewares