-
-
Notifications
You must be signed in to change notification settings - Fork 544
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
Add integration for flask and quart #149
Comments
🤦♂️ forgot that flask-graphql just targets a schema. Closing |
@davidroeca I think it might still be worth adding a view like the one we did for Django, so you don't need to install another package for this :) |
@patrick91 I would love to take a crack at this issue. |
@johnchuks assigned to you! :) |
Awesome! |
Is there still help wanted for this? |
Let's wait a couple of days for @johnchuks to answer :) otherwise I think you can work on this :) |
I asked about Strawberry + Quart over on the Quart gitter channel and Phil (Quart's author) had this interesting pattern:
I was able to integrate Ariadne directly into a Quart blueprint, but that doesn't really let you write a class-based View (with GraphQL) the way one typically would in Quart or Flask app, nor with Strawberry's dataclass syntax or advantages. I like Ariadne's approach, but for my current project/ experiment, I'm only working with a handful of tables and views and it feels like using a screwdriver to pound in a nail. If I had lots (maybe even a few dozen) of views/tables/schemas to worry about, I think Ariadne's approach might be a better fit. I'm not sure how you'd directly integrate Strawberry's ASGI pattern with Flask's WSGI architecture, so Phil's approach might be better for Flask than Quart. Haven't tried it. |
I'll close this issue for now as we have a Flask view now. We can always add a Quart view later, if needed (not sure if it is different from Flask) :) |
Any plans for implementations targeting flask or quart?
Alternatively, is there a standard way a third party could write a plugin for strawberry that targets an alternative framework? Asking because I like the design of
strawberry
models, but switching the entire framework leads to a pretty big migration rather than just swapping outgraphene
.The text was updated successfully, but these errors were encountered: