You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My code has not changed, I simply upgraded Graphene (graphene-python, graphene-django)
What is the current behavior?
Since upgrading to the latest versions (on Django 3.2.16), I have started getting the following errors when an exception is raised in my resolvers and mutations:
What is the expected behavior?
I expected everything to work as it used to before since I didn't change application code.
What is the motivation / use case for changing the behavior?
I was actually trying to get the latest version of the Graphiql GUI when I started. But then I noticed that my dependencies were very outdated.
My code has not changed, I simply upgraded Graphene (graphene-python, graphene-django)
Since upgrading to the latest versions (on Django 3.2.16), I have started getting the following errors when an exception is raised in my resolvers and mutations:
Everything was working fine before, until I upgraded to these versions:
What is the expected behavior?
I expected everything to work as it used to before since I didn't change application code.
What is the motivation / use case for changing the behavior?
I was actually trying to get the latest version of the
Graphiql
GUI when I started. But then I noticed that my dependencies were very outdated.Please tell us about your environment:
The text was updated successfully, but these errors were encountered: