Introspection schema returns empty values for input types about graphql HOT 12 CLOSED

Alright I think we're in business now. I was able to reproduce your issue in insomnia. There was an error when pulling in the locations for directives. It should be fixed now in v0.0.8. Sorry for the inconvenience!

from graphql.

Hey @danielvladco! Thanks for opening this. I think this issue belongs in the nautilus/graphql package. I'll move it over there for you.

I have some time to investigate this today so hopefully I'll have something for you soon

from graphql.

Okay so I've tried to see if I can reproduce your problem and I think I need a bit more information.

I ran the following code in a script and was able to find the fields for an input type:

// introspect the apis
schemas, err := graphql.IntrospectRemoteSchemas(
	"https://api.graphql.jobs/",
)
if err != nil {
	panic(err)
}

fmt.Println(schemas[0].Schema.Types["TagWhereInput"].Fields)

Is the payload you posted above a response from introspecting the gateway? Or is that the introspection query to one of the backend services?

from graphql.

Hi @AlecAivazis ,
Thanks for quick reply,

run this piece of code:

schemas, err := graphql.IntrospectRemoteSchemas(
	"https://api.graphql.jobs/",
)
if err != nil {
	panic(err)
}

, _ := json.Marshal(schemas[0].Schema.Types["TagWhereInput"])
fmt.Printf("%s/n", string(b))

notice how Kind field for input type is empty, when it's expected to be INPUT_OBJECT
also there are Fields but for some reason all their fields are resolved to zero values except for field Name and Type

You can introspect the endpoint directly and see all the mismatching fields.

from graphql.

Ah yea I noticed a similar inconsistency today while digging through this. I'll try to have a fix for you very soon. Sorry about this!

from graphql.

Okay i just pushed a fix that assigns the right Kind to input objects. I tested the script again and am able to interact with the API through the playground provided by the gateway.

Looking at the introspection query used in the gateway (the same used by most libraries) we only ask for name, description, defaultValue, and type information on input objects. Is something missing that you usually see with other introspections?

from graphql.

@danielvladco are you still seeing issues?

from graphql.

@AlecAivazis Unfortunately yes,

I use Insomnia as my graphql client and when it's trying to do introspection query I receive this error:

however when I use direct link It works fine

from graphql.

Okay that’s progress! Looks like insomnia is expecting a directive to be defined that isn’t. I’ll go download it and give it a try

from graphql.

Thanks, It seems to work now

You forgot a print here https://github.com/nautilus/graphql/blob/master/introspection.go#L196
:)

from graphql.

Whoops! Thanks for catching that. It should be gone now 😄

from graphql.

@danielvladco @AlecAivazis
In a real production ready example, there is no schema registry involved with nautilus?
"http://localhost:3004/query",
"http://localhost:3002/query",
"http://localhost:3006/query",
How do you dynamically update the service list?

from graphql.