-
Notifications
You must be signed in to change notification settings - Fork 470
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
allowMultiple #95
Comments
#132 plus #105 might have fixed this. params do
optional :number, type: Array, desc: "Favourite number" , values: [[1],[2],[3]]
optional :foo_or_bar , type: String, desc: "Foo or Bar?" , values: %w(Foo Bar)
end Is the behaviour for param number the behaviour you want? |
It looks like none of the specs actually test that allowMultiple can be generated. I'm trying to do this: optional :mapping, type: Hash, documentation: { is_array: true } do
requires :from, type: String, desc: 'Mapping done from'
requires :to, type: String, desc: 'Mapping goes to'
end relevant line in allowMultiple: is_array && data_type != 'array' && %w(query header path).include?(param_type) What am I missing here? And why can't multiple values be in the body? Thanks. |
impmented in actual versions |
Hello,
why can't I use the allowMultiple Fieldname described here:
https://github.com/wordnik/swagger-spec/blob/master/versions/1.2.md#524-parameter-object
Actually I want the multiple option box from:
http://petstore.swagger.wordnik.com/#!/pet/findPetsByStatus
There are predefined values for a parameter with an enum "available, pending, sold":
The text was updated successfully, but these errors were encountered: