-
-
Notifications
You must be signed in to change notification settings - Fork 762
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
additionalProperties doesn't work in exploded form query parameters #812
Comments
Thanks @dtkav, I will give it a try! |
I looked at that stackoverflow post in detail, and this looks like a bit of a nightmare to implement in connexion. Right now we loop through the list of query parameters, and for each one we look for a schema and try to cast it to the right type based on the matching schema. The main thing I can't figure out with this feature is that it's possible to have multiple parameter schemas that accept free-from keys, and they aren't namespaced!
and the query:
How are we supposed to pass this into the handler function? should it be:
or
or
I'll see if I can find out more info on the openapi github. |
The issue is only for exploded form query parameters. If you change the style to As @dtkav mentioned, there is no way to know how to validate As long as you don't enable |
Description
I am trying to accept dynamic parameters, i.e. parameters that are defined by the user and not known to me in advance of the request.
I was following this Stackoverflow example: https://stackoverflow.com/questions/49582559/how-to-document-dynamic-query-parameter-names-in-openapi-swagger
and wrote my yaml as
Expected behaviour
A GET to
/nodes?foo=bar
should return 200 and pass{'foo':'bar'}
to my function.Actual behaviour
A GET to
/nodes?foo=bar
returnsSteps to reproduce
Additional info:
Output of the commands:
python --version
:Python 3.7.0
pip show connexion | grep "^Version\:"
Version: 2.0.2
The text was updated successfully, but these errors were encountered: