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 only multi format is supported. This works fine for query strings where the same property is repeated for each value: ?items=a&items=b&items=c. For this case we have coercion to coerce single item to collection when needed.
Some parameters (headers) don't support this multi format and instead the collection needs to be represented as single string with separators. For this we need an coercer that can split an string using selected separator. This coercion should only be done when needed. Probably based on Schema record. For users, the API should be something like: :header-params [items (collection [s/Str] :csv)].
Determines the format of the array if type array is used. Possible values are:
csv - comma separated values foo,bar.
ssv - space separated values foo bar.
tsv - tab separated values foo\tbar.
pipes - pipe separated values foo|bar.
multi - corresponds to multiple parameter instances instead of multiple values for a single instance foo=bar&foo=baz. This is valid only for parameters in "query" or "formData".
The text was updated successfully, but these errors were encountered:
Swagger spec defines multiple ways to handle collections in string parameters (query, header, url encoded form params):
https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#parameter-object
Currently only
multi
format is supported. This works fine for query strings where the same property is repeated for each value:?items=a&items=b&items=c
. For this case we have coercion to coerce single item to collection when needed.Some parameters (headers) don't support this multi format and instead the collection needs to be represented as single string with separators. For this we need an coercer that can split an string using selected separator. This coercion should only be done when needed. Probably based on Schema record. For users, the API should be something like:
:header-params [items (collection [s/Str] :csv)]
.The text was updated successfully, but these errors were encountered: