__typename field on Input types about laravel-graphql

[cmizzi]

We used (before) GraphiQL for debugging purpose and the schema was broken due to union types (not supported by GraphiQL). So, we moved to insomnia and no problem with schema parsing.

I've got to look at some documentation/docs about __typename field on Input. Thanks for feedback!

[cmizzi]

GraphQL spec. tells that __typename is only used for Object, Interface, or Union.

Next, you're error is not really clear. typename should be called as __typename (into query or objects). Can you try an other plugins/softwares to try the schema introspection like insomnia ?

sudo snap install insomnia

and try the following GraphQL query ?

  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
                }
              }
            }
          }
        }
      }
    }
  }

[lorado]

Sorry, I didn't notice, that markdown parsed __ away, I edited the error, displayed by plugin.

I guess you misunderstood me =) So I'll try to describe what is going on.

When I create a Definition, then this lib generates much types, among other things also Input types. E.g. I have a definition for a user table. With an empty array in getMutable(), UserInput type looks like this: (this is a part of an output to your query above)

{
    "kind": "INPUT_OBJECT",
    "name": "UserInput",
    "description": null,
    "fields": null,
    "inputFields": [
        {
            "name": "id",
            "description": null,
            "type": {
                "kind": "SCALAR",
                "name": "ID",
                "ofType": null
            },
            "defaultValue": null
        },
        {
            "name": "__typename",
            "description": null,
            "type": {
                "kind": "SCALAR",
                "name": "String",
                "ofType": null
            },
            "defaultValue": null
        }
    ],
    "interfaces": null,
    "enumValues": null,
    "possibleTypes": null
}

So clearly for user mutation (user or users - so for creation of users), I can set following fields in input: id and __typename. The JS GraphQL Plugin on WebStorm reads the defined schema, and thinks: "What the heck, why do you want to set __typename in input, this is reserved by GraphQL" and don't work properly. When I removed __typename on input types, everything works like a charm.

Also for me looks this __typename on input pretty weird - I think no one will ever set this field in input... When you creates objects for you predefined table, you define only stuff for the DB. And there is no __typename. I guess even if you define something in __typename on input - it has no effect at all, or am I wrong?

Also here is how I understand docs. "It returns the name of the object type currently being queried." In docs is mentioned, that __typename is used on querying, and actually you can't query an input. Also: "This field is implicit and does not appear in the fields list in any defined type.". So even if you try introspect defined queried types, in my example User type (see below), there is no __typename field listed.

{
  "data": {
    "__type": {
      "kind": "OBJECT",
      "name": "User",
      "description": "Represents a User",
      "fields": [
        {
          "name": "id",
          "description": null,
          "args": [],
          "type": {
            "kind": "SCALAR",
            "name": "ID",
            "ofType": null
          },
          "isDeprecated": false,
          "deprecationReason": null
        },
        {
          "name": "email",
          "description": null,
          "args": [],
          "type": {
            "kind": "SCALAR",
            "name": "String",
            "ofType": null
          },
          "isDeprecated": false,
          "deprecationReason": null
        },
        {
          "name": "created_at",
          "description": null,
          "args": [],
          "type": {
            "kind": "SCALAR",
            "name": "Datetime",
            "ofType": null
          },
          "isDeprecated": false,
          "deprecationReason": null
        },
        {
          "name": "updated_at",
          "description": null,
          "args": [],
          "type": {
            "kind": "SCALAR",
            "name": "Datetime",
            "ofType": null
          },
          "isDeprecated": false,
          "deprecationReason": null
        }
      ],
      "inputFields": null,
      "interfaces": [],
      "enumValues": null,
      "possibleTypes": null
    }
  }
}

Summarised: I think, that __typename should not be explicitly defined in input Types, so it should be removed. It would solve compatibility problem with JS GraphQL plugin on PhpStorm, and also follow docs, at least how I understood it.

[cmizzi]

Ok. __typename is used to resolve morphTo relationship. We should probably not use GraphQL reserved words to do that. I'll check that and remove it from InputObject.