Strawberry integration doesn't work with newest strawberry-graphql release
#4037
Assignees
Labels
Comments
sentrivana
added a commit
that referenced
this issue
Feb 11, 2025
New Strawberry version removes the `execute` and `execute_sync` functions that we were monkeypatching in favor of integrating the code directly in `Schema.execute` and `Schema.execute_sync`. We were previously patching `execute` instead of `Schema.execute` that's calling it because that way we had access to a populated `execution_context` which contains data that we wanted to put on the event via an event processor. We have access to the `execution_context` directly in the extension hooks Strawberry provides, so we now add the event processor there instead of monkeypatching anything. This should also work for older Strawberry versions, so shouldn't be necessary to keep the old implementation around for compat. Closes #4037
|
A release with this in it will be out in the next couple of days! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The newest Strawberry version removes the
executeandexecute_syncfunctions that we were monkeypatching in favor of integrating the code directly inSchema.executeandSchema.execute_sync.We were previously patching
executeinstead ofSchema.executebecause that way we had access to a populatedexecution_contextwhich contains data that we wanted to put on the event via an event processor.We also have access to the
execution_contextdirectly in the extension hooks Strawberry provides, so we can add the event processor there instead of monkeypatching anything.The text was updated successfully, but these errors were encountered: