-
-
Notifications
You must be signed in to change notification settings - Fork 953
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
Deprecate built-in GraphQL support #1135
Conversation
@@ -36,6 +36,7 @@ markdown_extensions: | |||
- markdown.extensions.codehilite: | |||
guess_lang: false | |||
- mkautodoc | |||
- admonition |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like a clear yes to me. There are already several GraphQL specific projects that support ASGI (Strawberry, Ariadne, Tartiflette) (edit: just like you wrote in the docs :)), which makes them trivial to integrate within a Starlette based app (eg via submounting). Definitely better let specialized libraries deal with GraphQL which is an entire world by itself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what's left to figure out to get this merge able but what's here looks good to me. :)
I agree that this is the right direction to go in and I support this proposal. |
Cool, thanks. I guess I had two things in mind before merging this:
So for 2): |
@JayH5 No problem. Thank you! 🙂 |
I just want to say that I'm happy with this approach and that makes a lot of sense on doing it. Also, if this approach is followed the same way in the future, it will be cool. I'm saying this because the removal of UJSONResponse which represented a breaking change (even if it's easy to implement). |
I've tweaked the warning messages so that the Starlette version is mentioned in the docs rather than the code (since the code is already versioned but the docs are not). Thinking I'll keep #619 open until |
@tiangolo can you give recommandation ? Are you going to integrate something inside fast-api ? or let's people choose ? |
|
See #619
I'm trying to do some house-keeping so that we can better maintain Starlette. We need to either put some major work into the GraphQL integration (upgrade to Graphene 3, add a bunch of stuff people want), or deprecate it. I'm in favour of the latter, since there doesn't seem to be much interest in maintaining it among @encode/maintainers (myself included).
There are currently 11 open issues and 9 pull requests related to GraphQL. Meanwhile, the last real change to
GraphQLApp
was in October 2019 (#623).FastAPI does advertise GraphQL support via Starlette, but as far as I can tell doesn't actually integrate with it in any way.
This is a proposal and intended just to hopefully get the ball rolling and garner some discussion.