You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2023. It is now read-only.
I am on graphql-spring-boot-autoconfigure version 7.0.1. I suddenly see that graphql.tools.introspection-enabled is deprecated. The new property is graphql.tools.schema-parser-options.introspection-enabled but springboot can't find it neither is it accepted.
Can anybody point me to what am I doing wrong?
And because of this, I had managed to turn off introspection logging, now that's back on polluting the entire console. I have both the properties in my project and I don't know which ones working.
The text was updated successfully, but these errors were encountered:
I have the same problem @ubarua123. I am looking to disable introspection within my production environment, but neither the deprecated property graphql.tools.introspection-enabled or its suggested successor graphql.tools.schema-parser-options.introspection-enabled are working
@setchy Thanks for pointing out the workaround. I've reinstated the original property that is also still mentioned in the README. When set to false it'll instantiate the NoIntrospectionGraphqlFieldVisibility bean like your example. It'll log a warning about putting your server in contravention of the GraphQL specification when doing so.
I am on
graphql-spring-boot-autoconfigure
version7.0.1
. I suddenly see thatgraphql.tools.introspection-enabled
is deprecated. The new property isgraphql.tools.schema-parser-options.introspection-enabled
but springboot can't find it neither is it accepted.Can anybody point me to what am I doing wrong?
And because of this, I had managed to turn off introspection logging, now that's back on polluting the entire console. I have both the properties in my project and I don't know which ones working.
The text was updated successfully, but these errors were encountered: