-
Notifications
You must be signed in to change notification settings - Fork 139
Flask-GraphQL now returns warnings when using `graphql-core #71
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
Yes, the "_value" prefix has been added back in Core 2.3, to make the API consistent with GraphQL.js and Core 3 again. So this should be changed in Flask-GraphQL as well to remove the warnings. |
This only requires changes on the provided execute options in flask according to the executor. graphql-core diff 2.2.1 - 2.3 and bumping the minimum graphql-core version at setup.py, right? |
Yes. Of course it would be also great to have a flask-graphql v3 based on graphql-core v3. |
Now that the minimum version of
graphql-core
was bumped to>=2.3
we're now seeing warnings returning when running tests that leverageFlask-GraphQL
.Here's the relevant diff between
graphql-core
2.2.1
and2.3
:graphql-python/graphql-core@v2.2.1...v2.3.0#diff-a2c439ae03cccc507934c1377530d14aL74-L87
In
graphqlview.py
- arguments are being passed asroot
andcontext
though it seems these arguments are getting deprecated in favor ofroot_value
andcontext_value
.flask-graphql/flask_graphql/graphqlview.py
Lines 92 to 93 in 0137ca1
Here's the relevant
DeprecationWarning
The text was updated successfully, but these errors were encountered: