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
There are GraphQLTypeReferences in the schema when a recursive query like NodeGraphTest is used.
To Reproduce
On the integration test NodeGraphTest, we actually have a failing schema. If you inspect the schema after build, you will notice that the type of Node.parent is GraphQLTypeReference. This should never happen as all schemas should have the full objects.
You can add the following assert to now make a failing test
For what it's worth, I think the issue can be worked around by creating a new GraphQLTypeReference each time. The bug in graphql-java v11 is that it replaces each individual instance only once.
Library Version
0.2.7
Describe the bug
There are
GraphQLTypeReference
s in the schema when a recursive query like NodeGraphTest is used.To Reproduce
On the integration test NodeGraphTest, we actually have a failing schema. If you inspect the schema after build, you will notice that the type of
Node.parent
isGraphQLTypeReference
. This should never happen as all schemas should have the full objects.You can add the following assert to now make a failing test
Expected behavior
There are no
GraphQLTypeReference
in the code. This is fixed if I usegraphql-java
2019-03-07T04-34-55-809a980
The text was updated successfully, but these errors were encountered: