You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I implemented this library and immediately noticed that there is no example or documentation on how to include routing-controller's HttpErrors in the generated spec.
Is there a defined best-practice how to add the spec for a method that is able to throw e.g. a NotFoundError?
The text was updated successfully, but these errors were encountered:
No, there isn't. You could use the OpenAPI decorator to add a responses.404 property, or perhaps write another decorator that calls OpenAPI internally to save a bit of typing.
Please share here if you come up with a better solution!
I implemented this library and immediately noticed that there is no example or documentation on how to include routing-controller's
HttpError
s in the generated spec.Is there a defined best-practice how to add the spec for a method that is able to throw e.g. a
NotFoundError
?The text was updated successfully, but these errors were encountered: