-
-
Notifications
You must be signed in to change notification settings - Fork 295
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
OpenAPI - Single Query Param Key With Multiple Value #367
Comments
This is not supported yet, I will add it later. |
OK thanks will use a string for now then and update it when it's added. |
Adding this feature would probably also make this easier: #342 |
Released in poem/poem-openapi/tests/operation_param.rs Line 106 in dbe761a
|
Wow that was quick. Tested it out. Works perfectly. This project never ceases to amaze me. Thank you very much! |
I tried to copy paste this but i get the following error when i run it locally: Edit: I was using the wrong Query import. |
Hi,
Firstly thank you for this amazing project. It works really well and makes performant OpenAPI possible which is awesome. I'm trying to implement sorting. Something along the lines of https://specs.openstack.org/openstack/api-wg/guidelines/pagination_filter_sort.html#sorting
Using
param::Query<Vec<String>>
does allow multiple values through swagger ui however they conflict by creating a key for each value as explode is set to true by default and I only get access to the last entry of this vec. How would I set explode to false? https://stackoverflow.com/questions/62527254/how-does-open-api-3-0-support-a-single-query-param-key-with-multiple-valuesI can set the query param as a string and manually split the comma separated value entered but would rather it is properly documented in swagger ui as an array.
The text was updated successfully, but these errors were encountered: