-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Support GraphQL-core 3.3 #577
base: main
Are you sure you want to change the base?
Support GraphQL-core 3.3 #577
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Ping me on discord if you need help on fixing the issues on the broken tests
@@ -45,6 +45,9 @@ jobs: | |||
django-version: | |||
- 4.2.* | |||
- 5.0.* | |||
graphql-core-version: | |||
- 3.3.0a5 | |||
- 3.2.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe 3.2.*
, just to make sure we get the latest patch release, like we do for django?
Not sure if 3.3.*
would work as it is a pre-release, and usually those have to be totally hardcoded
try: | ||
from graphql.execution.collect_fields import collect_sub_fields | ||
except ImportError: | ||
from graphql.execution.collect_fields import collect_subfields as collect_sub_fields |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably will need to type ignore this line
Description
Types of Changes
Issues Fixed or Closed by This PR
Checklist