-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
GraphQL support #2288
Comments
What's wrong to have it as standalone extension which provides extras to integrate graphql with aiohttp? You there depends on aiohttp in anyway. What kind of support aiohttp have to provide? |
That’s exactly what it is. This project is not a fork and pull request, I just wanted the community to be aware of it. I’m not sure of what they best place to share this info, so I created this issue. |
Sorry, I took your issue a bit different way. How about docs? We have there section about third parties and extensions. Feels like the best place to share. |
Cool. As this project gets sucked into the |
@dfee feel free to make a PR for mentioning the library in our third parties. I'm closing the issue -- the tracker is overwhelmed by bug reports and feature proposals. |
Added aiohttp-graphql Ref: aio-libs#2288 fixed typo
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs. |
I built a GraphQL component for
aiohttp
named aiohttp-graphql (i.e.pip install aiohttp-graphql
).The premise is simple: Just provide a schema and attach the view to the route:
And then you'll be able to access both GraphQL and GraphiQL on
/graphql
. There are many configuration options, so RTFD.I just wanted to put this here for future users. Thanks
aio-libs
folks for maintaining good libraries to build on top of. Cheers –The text was updated successfully, but these errors were encountered: