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
Right now the OpenApi definition does not provide a schema for the GET responses.
Those definitions already exists (they are e.g. used for POST parameters) and it would be nice to also have them included in the GET responses.
This would make the API definition more complete and enable clients, for example swagger-ui, to always show the model or even example results of the endpoint.
See for example: http://petstore.swagger.io/#!/pet/getPetById
Currently the OpenApi definition for a GET endpoint response looks like this:
Right now the OpenApi definition does not provide a schema for the GET responses.
Those definitions already exists (they are e.g. used for POST parameters) and it would be nice to also have them included in the GET responses.
This would make the API definition more complete and enable clients, for example swagger-ui, to always show the model or even example results of the endpoint.
See for example: http://petstore.swagger.io/#!/pet/getPetById
Currently the OpenApi definition for a GET endpoint response looks like this:
Including the schema would look like this:
The text was updated successfully, but these errors were encountered: