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
I've used Swagger codegen to create a client in Python.
But when implementing the reading of report data I noticed issues with the ReportV1 definition and API response:
The OpenApi ReportV1 definition is not consistent with usage of capital letters, some fields are all lowercase, while some fields use uppercase for first letter in word. BTW also odd anomaly the usage of underscore in this part of definition but not in the rest.
The actually response from the API call is not consistent with the OpenApi definition, which means that the Swagger client can't import the values since the field names doesn't match.
There are two fields that doesn't exist in the OpenApi definition but exists in the API response.
There is one field that doesn't exist in the API response but exists in the definition.
I've used Swagger codegen to create a client in Python.
But when implementing the reading of report data I noticed issues with the ReportV1 definition and API response:
The OpenApi ReportV1 definition is not consistent with usage of capital letters, some fields are all lowercase, while some fields use uppercase for first letter in word. BTW also odd anomaly the usage of underscore in this part of definition but not in the rest.
The actually response from the API call is not consistent with the OpenApi definition, which means that the Swagger client can't import the values since the field names doesn't match.
There are two fields that doesn't exist in the OpenApi definition but exists in the API response.
There is one field that doesn't exist in the API response but exists in the definition.
Se attach excel file for details.
API ReportV1 bugs.xlsx
The text was updated successfully, but these errors were encountered: