-
-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
errorFormatter returns invalid openapi schema #205
Comments
I would suggest adding an option to override errorResponseObject with your own error object |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello, Any news on this topic ? I'm having a use case where I try to add some data to a 409 error (the conflicting object). |
is there even a reason to limit the shape of the response body? I think that's the purpose of the trpc errorFormatter that we're all using, I think trpc-openapi should just take the error object as it is and pass it on... |
I've been using errorFormatter to include Zod errors and more custom errors, but the returned
error type in openapi schema doesn't synchronize
trpc error formatter:
return open-api schema:
real response:
The text was updated successfully, but these errors were encountered: