-
Notifications
You must be signed in to change notification settings - Fork 9.2k
Updates to parameter and requestBody #884
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
Conversation
|
|
|
Reusing the name from https://tools.ietf.org/html/rfc6570#section-3.2.2, like the other |
|
OK sure, but it still sucks |
|
Alternatives welcome. |
|
|
|
We can discuss it tomorrow. I don't think it's a good idea because unlike in 2.0, it cannot be applied to
|
|
Were there still open issues here? I thought we resolved everything. |
|
Per our discussion, changed the default value of |
Updates to parameter and requestBody
Summary of changes:
commaDelimitedtosimple, reference the type in the RFC and made not applicable toquery. Described behavior for primitive value, added exploded example.stylebased on parameter type.allowEmptyValueis inapplicable if example table value isn/a.styleofx-www-form-urlencodedtoform, set behavior to be likequeryparameters.contentTypenot required, described default values.Note that the behavior of
headeerandcookieparameters is different than what we discussed.headerFor values
[ red, green, blue ]:will be
colors: red,green,blueregardless of whetherexplodeis true/false.This is different than the discussed result of
explodetrue represented as:colors: colors=red&colors=green&colors=blue.cookieBy following
stylebeingform, we get the representation ofSet-Cookie: colors=red,green,blueby default, so no extra explanation needed (unlike usingsimple).Open issues:
explodebeingtrueforcookieparameter will look like?collectionFormatby default bemultiand notcsv. This means that we should setexplodetotrueforqueryparameters by default. It's a cumbersome explanation (if this then that, otherwise something else), but doable. Opinions welcome.