When calling an API with multiple operations in one call, while using non-blocking GraphQL mode Quarkus, the injected context refers to the last operation instead of the context of the "child" field in Parent1.
Using quarkus.smallrye-graphql.nonblocking.enabled=false fixes the behaviour.
Expected behavior
The correct context should be injected and the call result should look like:
Describe the bug
Given following setup:
When calling an API with multiple operations in one call, while using non-blocking GraphQL mode Quarkus, the injected context refers to the last operation instead of the context of the "child" field in Parent1.
Using
quarkus.smallrye-graphql.nonblocking.enabled=false
fixes the behaviour.Expected behavior
The correct context should be injected and the call result should look like:
Actual behavior
The actual result looks like:
How to Reproduce?
Reproducer: https://github.com/ddelbondio/quarkus-graphql-context-bug
Steps to reproduce:
Output of
uname -a
orver
Microsoft Windows [Version 10.0.19045.2130]
Output of
java -version
openjdk version "11.0.12" 2021-07-20 OpenJDK Runtime Environment Temurin-11.0.12+7 (build 11.0.12+7) OpenJDK 64-Bit Server VM Temurin-11.0.12+7 (build 11.0.12+7, mixed mode)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.13.3.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Additional information
No response