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
Currently the specification doesn't support complex formData parameters. For example, our API uses this format (appropriately escaped):
body={"name1": "value", "name2": "value2"}
With the current spec we'd have to specify the body parameter as type: string and pass the JSON as an opaque string. This negates a lot of the value of the Swagger definition for our API.
@fdstevex FYI complex parameters have been added to the spec. What @ePaul mentions is that we haven't formalized how we describe the serialization strategy. But what you're asking for has been accepted conceptually.
Currently the specification doesn't support complex formData parameters. For example, our API uses this format (appropriately escaped):
body={"name1": "value", "name2": "value2"}
With the current spec we'd have to specify the body parameter as type: string and pass the JSON as an opaque string. This negates a lot of the value of the Swagger definition for our API.
As also described here:
https://groups.google.com/forum/#!topic/swagger-swaggersocket/Eftccv6z5Ss
and
https://groups.google.com/forum/#!searchin/swagger-swaggersocket/formData$20schema%7Csort:relevance/swagger-swaggersocket/6QxOTKLZyM0/49o4FRR8IgAJ
The text was updated successfully, but these errors were encountered: