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
According to the spec, only the top-level fields are required to be executed sequentially (at least for mutations, couldn't find anything about subscriptions requiring them to be executed serially). Ideally, we'd want to execute the top-level fields of mutations sequentially, but execute any child fields using the user-provided execution mode.
The text was updated successfully, but these errors were encountered:
Came across this while optimizing the Executor. Currently we force the execution of mutations and subscriptions to sequential mode
caliban/core/src/main/scala/caliban/execution/Executor.scala
Lines 43 to 47 in 078c28d
According to the spec, only the top-level fields are required to be executed sequentially (at least for mutations, couldn't find anything about subscriptions requiring them to be executed serially). Ideally, we'd want to execute the top-level fields of mutations sequentially, but execute any child fields using the user-provided execution mode.
The text was updated successfully, but these errors were encountered: