Open crazyscientist opened 3 years ago
Have the same problem
Seems like it was caused by adding support for GraphQL Core 3. See https://github.com/tfoxy/graphene-django-optimizer/commit/e5c57fc8e15691d37efde2af60f70e9e787e4344
Unfortunately, v0.9.0 wasn't marked as breaking changes for some reason...
Thanks for bringing this up. As @KristobalJunta said, the breaking change was brought by adding support for GraphQL Core 3. Will add a message to the readme so people are aware of this.
Added note to readme. If someone knows a way to warn about version incompatibility with pip
, please let me know. Will leave this issue open so that people can find it easier.
If someone knows a way to warn about version incompatibility with
pip
I'm not aware of such a feature in pip
. But you could use Python's warning
module to generate a warning at runtime :thinking:
On the same boat using graphene-django==2.15.0
but with no graphene
and currently using graphene-django-optimizer==0.6.2
. Should the move be to scrap graphene-django
(updates are too slow) and just use graphene v3
with graphene-django-optimizer==0.9.0
?
When using these packages:
the following exception gets raised when running tests or accessing the GraphiQL interface:
With version 0.8.0 this exception does not get raised.