-
Notifications
You must be signed in to change notification settings - Fork 70
graphql-server v3.0.0b1 does not work with aiohttp in async mode with graphiql #64
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
Comments
Thank you for this fix. The problem I was observing was in an aiohttp app that called:
Setting
|
I didn't noticed these issues (weren't at my notifications list), but gonna checkout the linked PR and provide extra tests for handling this case. Thank you 🚀 |
* Fix enable_async=True in aiohttp Apply the fix suggested by ketanbshah in #64 * Apply the same fix to sanic * tests: add tests for graphiql enabled plus async Co-authored-by: Manuel Bojato <30560560+KingDarBoja@users.noreply.github.com> Co-authored-by: KingDarBoja <stevenbojato04@gmail.com>
Next release will contain this change :) Thanks for reporting and submitting a PR. |
Uh oh!
There was an error while loading. Please reload this page.
I had to change graphqlview.py at line 155 as follows
from
The text was updated successfully, but these errors were encountered: