Input Object fields about graphql-spec

[leebyron]

Can you share the introspection query in particular? GraphQL does not have a concept of keyed sets or maps, only lists, so I'm a little confused with the issue.

inputFields and fields have different names in introspection because they return different types. Since introspection uses one simplified and flattened "__Type" type that can represent all of the types in a type system, it needs differently named fields to refer to these two different concepts.

[HurricaneJames]

Apologies, I think I was confused. No, I was definitely confused. There is not a lot of literature on mutations in GraphQL, and therefore not a lot of literature on really big blobs of data in Input Objects. I was trying to tease out the implementation of GraphQL-JS vs the actual spec and Object vs Input Object.

I went back and ran the introspections again now that I have significantly more experience with Input Object, I think perhaps I was leaving out the name field, which made the two seem different. Also, defining fields on the GraphQL-JS GraphQLInputObject, but introspecting on inputFields was causing some confusion (I created a separate ticket for that issue on that project (graphql/graphql-js#144).

Sorry for wasting your time on this.

[leebyron]

No problem, this has been good feedback!