-
-
Notifications
You must be signed in to change notification settings - Fork 769
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
query params of type object with style: form
are not being deserialized
#1291
Comments
Thanks for the report @Halkcyon. Connexion currently doesn't deserialize query objects with |
Related to #963 |
style: form
are not being deserialized
Since it's a pretty old thread, but it's still open, @RobbeSneyders is this still a bug in Connexion 3? An example, we'd like to specify query parameters like this:
This would auto-include any User property and make it possible to define query filters on any User field. This way, we don't have to re-define each user property as an individual query parameter. With strict validation, Connexion does not respect this specification and rejects all query parameters. |
Description
When defining objects to take through a query string, they are not being deserialized in my app code. The function parameter is being passed an empty dict, but
request.form
definitely sees the proper values.Expected behaviour
The params are deserialized into a
dict
and passed into my view.Actual behaviour
The params show up on
request.form
, but are not being deserialized; I receive an emptydict
for the key defined in my spec.Steps to reproduce
Additional info:
Output of the commands:
python --version
pip show connexion | grep "^Version\:"
The text was updated successfully, but these errors were encountered: