-
Notifications
You must be signed in to change notification settings - Fork 9k
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
UI does not show request body #273
Comments
swagger-ui is only designed to display the response body |
Do you want to eloborate? These seems like a silly response to me in my humble opinion. Why does SwaggerUI only show responses? Would it not be nice to see the exact request that is being sent, ideally as a JSON object? |
I think it depends on what swagger-ui is being used for. If interactive documentation, then the inputs for the request are the right scope of information. If as a debugging tool, then yes I can understand why you'd want to have the full raw request. If that's your goal, I'd suggest forking the UI and rendering the data--everything is available in the underlying swagger-js library. |
Raw request vs "inputs for the request" is a pedantic distinction at this point - Swagger doesn't display request bodies in any form currently. All you can see is the output, not the input. As documentation for a web API, Swagger shows you only half of the information required to form a usable POST request. |
I don't follow your distinction between request bodies and request parameters. |
Oh sorry, I thought this was basic HTTP terminology.
|
Since you opened #771, let's keep the correspondence there. |
Swagger-UI does not appear to show the request body in interactive "Try it out!" operations.
For example, see the wordnik api doc for authenticating the user using a POST request:
http://developer.wordnik.com/docs.html#!/account/authenticatePost_post_1
The text was updated successfully, but these errors were encountered: