Skip to content
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

In webargs 6, use_args will accept a single location #75

Open
lafrech opened this issue Dec 22, 2019 · 6 comments
Open

In webargs 6, use_args will accept a single location #75

lafrech opened this issue Dec 22, 2019 · 6 comments

Comments

@lafrech
Copy link

lafrech commented Dec 22, 2019

Hi.

Just a friendly heads up about this change coming in the next major webargs version.

marshmallow-code/webargs#420

Do you foresee any issue with this?

@maximdanilchenko
Copy link
Owner

@lafrech, hi!

Thank you for this information!

I will try to make needed changes as soon as possible to make it compatible with webargs 6.

@rch9
Copy link

rch9 commented Jun 5, 2020

Hi.

I have an issue using 'webargs==6.1.0' and validation_middleware.
It works with 'webargs==5.5.3'

python3.7/site-packages/aiohttp_apispec/middlewares.py", line 34, in validation_middleware
schema["schema"], request, locations=schema["locations"]
TypeError: parse() got an unexpected keyword argument 'locations'

I can take a look a bit later and make PR.

@lafrech
Copy link
Author

lafrech commented Jun 5, 2020

This lib is not compatible with webargs 6 (yet ?).

@maximdanilchenko
Copy link
Owner

@rch9 it would be great if you can take a look!

@kiforchuk
Copy link
Contributor

@maximdanilchenko Can be closed
Fixed by #112

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants