Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for type: object for formData parameters #758

Closed
fdstevex opened this issue Aug 10, 2016 · 2 comments
Closed

Support for type: object for formData parameters #758

fdstevex opened this issue Aug 10, 2016 · 2 comments

Comments

@fdstevex
Copy link

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

@ePaul
Copy link
Contributor

ePaul commented Aug 10, 2016

Related: #665.

@fehguy
Copy link
Contributor

fehguy commented Aug 11, 2016

@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.

Please reopen with any questions.

@fehguy fehguy closed this as completed Aug 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants