enabling graphql.servlet.maxQueryDepth causes playground docs/schema to never load

[bryevo]

Enabling the graphql.servlet.maxQueryDepth property to an arbitrary value causes the graphql playground docs and schema tabs to never load and stays "spinning" infinitely.

This also seems to be affecting Voyager, if installed.

After I removed this property in my application.yml file, my docs and schema are working fine.

Using v11.1.0 of graphql-spring-boot

[gabbigum]

Can you share more information? Maybe your pom.xml file?

I've tried setting this property on my graphql server using the same version of graphql-spring-boot and my playground seems to work fine.

[DevelopmentBaxter]

Yes, I got the same problem.

            <dependency>
                <groupId>com.graphql-java</groupId>
                <artifactId>graphql-java</artifactId>
                <version>14.0</version>
            </dependency>
            <dependency>
                <groupId>com.graphql-java-kickstart</groupId>
                <artifactId>graphiql-spring-boot-starter</artifactId>
                <version>8.0.0</version>
            </dependency>
            <dependency>
                <groupId>com.graphql-java-kickstart</groupId>
                <artifactId>graphql-spring-boot-starter</artifactId>
                <version>8.0.0</version>
            </dependency>
            <dependency>
                <groupId>com.graphql-java-kickstart</groupId>
                <artifactId>graphql-java-tools</artifactId>
                <version>6.1.0</version>
            </dependency>
            <dependency>
                <groupId>com.graphql-java</groupId>
                <artifactId>graphql-java-servlet</artifactId>
                <version>6.1.3</version>
            </dependency>

graphql.servlet.maxQueryDepth=10 #This causes the problem

[setchy]

Hi @bryevo @DevelopmentBaxter - same reason as shared in #672.

GraphQL Tooling such as Playground, Voyager, Altair, GraphiQL etc all perform introspection queries in order to build their experience. Example introspection query below to show the type of depth this query has

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

[oliemansm]

@setchy Think this issue should be converted into a Q&A Discussion instead with your comment as the accepted answer. This is not a bug or problem on our end imo, but simply expected behavior. Do you agree?

[setchy]

I agree @oliemansm 😃