Closed tschig closed 1 year ago
Thanks for opening this, not sure I understand the issue (or have a solution in mind) but should be handled
The issue: API Specification (swagger) and API Implementation are different. Possible Solution: Generate API Specification automatically from the Implementation code.
Closing as there is another ticket to fix the API Docs
Describe the issue Example: Lists all media GET /media Response says it will respond with an array of medias, but in reality the server response with an object that includes meta data and a result key with the actual response array.
Why is this a problem? When we generate a java SDK with swagger codegen, the generated client expects an array, but an object is returned and therefore the deserialization process fails.
To Reproduce Steps to reproduce the issue:
Expected behavior Either: Swagger Doc is adapted so that the correct response is specified. Or: Server returns Specified response (Array of media)
Additional context
Response from Server:
Example/spec in swagger: