In my use case, KGraphQL is resolving fields lazily using Exposed. However, even when installing a hook in the pipeline at Setup which wraps the call in a newSuspendedTransaction block, it seems the dispatcher-based design of KGraphQL ignores it. Similarly, I tried creating a custom dispatcher:
however this still raises the "No transaction in context" error.
Alternatively, would it be possible to provide a RequestExecutor which does not dispatch each field and instead iterates over each, all on the same coroutine context in which the call happens so setups like this could work?
In my use case, KGraphQL is resolving fields lazily using Exposed. However, even when installing a hook in the pipeline at Setup which wraps the call in a
newSuspendedTransaction
block, it seems the dispatcher-based design of KGraphQL ignores it. Similarly, I tried creating a custom dispatcher:however this still raises the "No transaction in context" error.
Alternatively, would it be possible to provide a RequestExecutor which does not dispatch each field and instead iterates over each, all on the same coroutine context in which the call happens so setups like this could work?