Closed marceloverdijk closed 6 years ago
Hmm looking at the Firefox request it seems it's not including the query. Looking at the Firefox dev tools I see the query is sent as request parameter:
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 } } } } } } } }
but it does not contain the \n
.
I tested with another (working) implementation and I see in Chrome the same \n
but there it is working. So it seems an issue on my side. Don't know what yet but will close this one.
I'm running against an issue with
v0.11.11
but also tested the same issue withv0.11.10
.The initial introspection call seems to contain invalid json in chrome, but works in chrome.
When copying the request as cURL I see in Chrome the the json contains
\n
characters.This is the cURL request from Chrome:
it contains:
And this the one from Firefox:
Because of the error the docs are not populated in Chrome, but are in Firefox.
I'm hosting the graphl endpoint in localhost, so I cannot point to it why it's working in Firefox, but not in Chrome...