-
-
Notifications
You must be signed in to change notification settings - Fork 77
TypeError thrown during introspectSchema #49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
While debugging this I managed to extract the actual graphql query that query IntrospectionQuery {
__schema {
queryType { name }
mutationType { name }
subscriptionType { name }
types {
...FullType
}
directives {
name
description
locations
args {
...InputValue
}
}
}
}
fragment FullType on __Type {
kind
name
description
fields(includeDeprecated: true) {
name
description
args {
...InputValue
}
type {
...TypeRef
}
isDeprecated
deprecationReason
}
inputFields {
...InputValue
}
interfaces {
...TypeRef
}
enumValues(includeDeprecated: true) {
name
description
isDeprecated
deprecationReason
}
possibleTypes {
...TypeRef
}
}
fragment InputValue on __InputValue {
name
description
type { ...TypeRef }
defaultValue
}
fragment TypeRef on __Type {
kind
name
ofType {
kind
name
ofType {
kind
name
ofType {
kind
name
ofType {
kind
name
ofType {
kind
name
ofType {
kind
name
ofType {
kind
name
}
}
}
}
}
}
}
} |
Here should be added additional check |
OK thank you for having a look and confirming. I will dig more into the code and see if I can send a PR. |
I think the page being parsed where the problematic data comes from is https://www.elastic.co/guide/en/elasticsearch/reference/6.1/search-search.html |
Fixed. A new version on npm already |
I am attempting to link our
graphql-compose-elasticsearch
API with another API viagraphql-tools
. I am not able to get theintrospectSchema(link)
call to succeed. It throws an exception which looks to be coming from thegraphql-compose-elasticsearch
response to the introspection query.At one point I was able to reproduce the error with the query below, although at the moment this query is now running properly. That's why I'm confident the error is originating in graphql-compose-elasticsearch. However, the
introspectSchema(link)
call is still failing with the error below.That
defaultValue
seems to be the minimum case required to trigger the error. Here's the error I see in the response (value truncated beyond the interesting part)The text was updated successfully, but these errors were encountered: