Update dependency gql to v4 #226
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>=3.4.1,<4->>=4,<5Release Notes
graphql-python/gql (gql)
v4.0.0Compare Source
Breaking Changes
This is a big change:
gqlanddsl_gqlmethods will now return aGraphQLRequestinstead of aDocumentNodea
GraphQLRequestis an object containing the document and optionalvariable_valuesandoperation_nameexecuteandsubscribemethods now receive aGraphQLRequestas main argument instead ofa
DocumentNode,variable_valuesandoperation_nameargumentsvariable_valuesas an argument ofexecuteorsubscribestill works but is deprecatedSee https://gql.readthedocs.io/en/latest/usage/variables.html for the new syntax.
Previously if a task was cancelled while a subscription task was active,
the
asyncio.CancelledErrorException would be swallowed by our code.This is not the case anymore so you should now trap that Exception yourself.
The file upload functionality has been modified to require
FileVarinstancesfor uploaded files (the old method still works but is deprecated).
See https://gql.readthedocs.io/en/latest/usage/file_upload.html
Note that some backends might not support this and return
Unknown argument includeDeprecated. See #564Now gql will trap Exceptions raised by dependencies when executing a request and will
encapsulate that Exception into the
TransportConnectionFailedExceptionTransportConnectionClosedException replacingConnectionClosedException (#536)websocketattribute removed from transport, now using_connectedinstead (#536)Features
Batching requests is now fully supported, on sync or async transports, with automatic batching:
See https://gql.readthedocs.io/en/latest/advanced/batching_requests.html
Fixes
Fix httpx test deprecated warning (#542)
Refactor websockets transports (#536) :
Refactor WebSockets Transport with Dependency Injection Architecture
This major architectural improvement implements dependency injection patterns across the WebSockets transport layer, creating a more modular, testable, and extensible system:
Misc
v3.5.3Compare Source
v3.5.2Compare Source
Now supporting graphql-core v3.2.4 again (See issue #534)
v3.5.1Compare Source
3.5.1
Issue #529 reported that by default the
AIOHTTPTransportwas not validating ssl certificates(a self-certificate was accepted by default).
This version adds a warning to warn users (See PR #533).
As a workaround, using
ssl=Truein the transport arguments fix the issue.graphql-corehas been restricted to<3.2.4to fix tests.A new stable version will be made shortly.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.