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'm having a problem with an openapi.json specification that contains a response defined as a object that can have keys as strings, something like in the Swagger doc - Value Type
API response
{
"data": {
"fooId": "123",
"bar": "abc"
}
}
External API that I don't have control over, defines:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi
I'm having a problem with an openapi.json specification that contains a response defined as a object that can have keys as strings, something like in the Swagger doc - Value Type
API response
External API that I don't have control over, defines:
OpenApi.json
The returned model seems wrong as it expect explicit attributes "key" and "value"
I could not find any end 2 end test for this case of specification for additionalProperties. Is this a expected model output or probably a bug?
Beta Was this translation helpful? Give feedback.
All reactions