We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello - thanks for this great library !
I spotted an issue with 'data' vs 'json' in aiohttp_stubs vcr_request. When only json is present, vcrpy fails to record
aiohttp_stubs
vcr_request
The default fallback (from data to json) works when data is missing in the kwargs, but recent versions of aiohttp _request seems to have data = None when json is present (see @https://github.com/aio-libs/aiohttp/blob/40d8eb88de7674efbd6b001d04c0b91dad1f42d1/aiohttp/client.py#L375C11-L375C11)
The text was updated successfully, but these errors were encountered:
I noticed the same thing. I think the solution is for vcrpy to pull json first and fallback to data. I have a PR with the change here: #768
json
data
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Hello - thanks for this great library !
I spotted an issue with 'data' vs 'json' in
aiohttp_stubs
vcr_request
. When only json is present, vcrpy fails to recordThe default fallback (from data to json) works when data is missing in the kwargs, but recent versions of aiohttp _request seems to have data = None when json is present (see @https://github.com/aio-libs/aiohttp/blob/40d8eb88de7674efbd6b001d04c0b91dad1f42d1/aiohttp/client.py#L375C11-L375C11)
The text was updated successfully, but these errors were encountered: