We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Do all clients need to inspect the schema at runtime?
If not would it be possible to optionally not expose the schema? If so I'd probably want to do that in production.
The text was updated successfully, but these errors were encountered:
@molexx It makes sense. I can add configuration property to GraphQLJpExecutor to apply NoIntrospectionGraphqlFieldVisibility to the schema if enabled.
GraphQLJpExecutor
NoIntrospectionGraphqlFieldVisibility
Sorry, something went wrong.
@molexx This should be possible to achieve with NoIntrospectionGraphqlFieldVisibility implementation that already exists in Graphql Java:
https://github.com/graphql-java/graphql-java/blob/master/src/main/java/graphql/schema/visibility/NoIntrospectionGraphqlFieldVisibility.java#L17
After fixing GH-239, it should be possible to apply NoIntrospectionGraphqlFieldVisibility via Supplier instrumentation per request.
Yes, tested with #239 and NO_INTROSPECTION_FIELD_VISIBILITY following the example with a @RequestScope Supplier<GraphqlFieldVisibility. Thanks!
@RequestScope
Supplier<GraphqlFieldVisibility
No branches or pull requests
Do all clients need to inspect the schema at runtime?
If not would it be possible to optionally not expose the schema? If so I'd probably want to do that in production.
The text was updated successfully, but these errors were encountered: