Closed traviscook21 closed 4 years ago
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
: https://github.com/graphql-python/graphql-core/compare/v2.2.1...v2.3.0#diff-a2c439ae03cccc507934c1377530d14aL74-L87In
graphqlview.py
- arguments are being passed asroot
andcontext
though it seems these arguments are getting deprecated in favor ofroot_value
andcontext_value
.https://github.com/graphql-python/flask-graphql/blob/0137ca1315d811a7e01a1d256e41c74bc1c3fc2c/flask_graphql/graphqlview.py#L92-L93
Here's the relevant
DeprecationWarning