Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabling introspection by introspectionEnabled #499

Open
BergJonatan opened this issue Apr 20, 2021 · 0 comments
Open

Disabling introspection by introspectionEnabled #499

BergJonatan opened this issue Apr 20, 2021 · 0 comments
Labels

Comments

@BergJonatan
Copy link

Description

Disabling introspection by setting introspectionEnabled to false does not work

Expected behavior

Field types that starts with __ is blocked and not exposed.

Actual behavior

Field types such as __typename is included in the response

Steps to reproduce the bug

  1. Create GraphQLSchema bean where you return something like this:
    return SchemaParser .newParser() .file(GRAPHQL_SCHEMA) .resolvers( new RootResolver(someStorage), new SomeOtherResolver(anotherService) ) .dictionary(SomeGraphQlType.getName(), SomeGraphQlType.class) .scalars(JsonObjectScalar.JSON) .options(SchemaParserOptions.newOptions().introspectionEnabled(false).build()) .build() .makeExecutableSchema();
  2. Make a graphql query that returns a type
  3. Confirm that the __typename information exists
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant