We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Swagger-UI is able to document errors with responseModels. grape-swagger has implemented this feature too.
Now it would be nice, when I could present my errors with an entity directly, for instace like this:
error!({ code: 'deleted', with: Iron::Entities::Error, message: "Account has ..." }, 410)
The text was updated successfully, but these errors were encountered:
👍
Sorry, something went wrong.
This depends on #85 Also it would be nice when the error formatter can access the status code directly and not only with
env['api.endpoint'].status
This was #705, closing.
No branches or pull requests
Swagger-UI is able to document errors with responseModels. grape-swagger has implemented this feature too.
Now it would be nice, when I could present my errors with an entity directly, for instace like this:
The text was updated successfully, but these errors were encountered: