Yes 202 is the appropriate and common response for POST requests.
It would be great if the doc matches the response. This will prevent errors from rising on the client side.
I also found another issue;
The post methods are defined in the swagger document to return a 200 status code. However, the actual response is 202:
// YAML version swagger doc
post:
tags:
- "generator"
description: "Send a command to the generator "
parameters:
-...
I don't think an openapi 3.0.0 version declaration will cut this. The spec has properties as host, basePath, schemes, definitions which are swagger 2.0 definitions and are not accepted by openapi 3.0.0 standard.
I understand that SparkSwagger's main focus is with swagger-UI. Whereas...
Not sure if this is the place to add bug reports; If not, please let me know.
Issue:
The swagger spec definition has a mix of OpenAPI versions syntax:
"/application/commands": {"get": {"tags": [],"description": "Get the list of commands ","parameters": [],"responses": {"200": {"description"...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.