-
Notifications
You must be signed in to change notification settings - Fork 38
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 parameterized collections as api parameters #7
Comments
+1 on this feature :) |
@deslauriersp can you give me more detail on this e.g. example of your method signature and what form the http request should take to pass the list/array parameter? It looks like the swagger 1.2 spec does not handle array parameters well e.g. handle different formats of multi valued params like &p1=val1&p1=val2 versus &p1[]=val1&p1[]=val2 versus &p1=val1,val2 the latter CSV one appears to be the main one supported by the UI for the 1.2 spec.. |
Given your question, maybe I misunderstood what was the issue #7 about.
json model generation works. But it fails for collections (with or without
|
@deslauriersp your use case should be supported e.g. i have a test for this that works: @post are you sure you aren't missing a http method like @post? After looking back into this it isn't arrays that I was thinking of but rather a generic parameter class e.g. Gen and with a method like postVal(List<Gen> x) |
duplicates #136 |
also duplicates conorroche#10 |
support parameterized collections as api parameters
The text was updated successfully, but these errors were encountered: