A modern programming language that makes developers happier.

kotlinlang

Hello! The gradle plugin will add a deprecated annotation to classes when a deprecated mutation/query is used and generated code for. For example `w: file://.../operations/adapter/<name>_ResponseAdapter.kt:46:79 '@Deprecated(...) val ...' is deprecated. Deprecation reason here.` Is is possible to configure that these warnings should be treated as errors rather than warnings? :thinking_face: (Or some earlier error if deprecated mutations/queries are used)

I would prefer to not make all warnings from other parts also errors, thinking maybe if it was possible to configure the level property of the annotation that is generated?

actually you can also use `failOnWarnings.set(true)` which will fail the codegen whenever a warning is encountered (that includes using deprecated fields in operations)

Oh, interesting! That will do. Thanks :blush:

Is that failOnWarnings an Apollo configuration or an overall config somewhere? Trying to understand how it's different than allWarningsAsErrors

yes it's declared <https://apollographql.github.io/apollo-kotlin/kdoc/apollo-gradle-plugin-external/com.apollographql.apollo.gradle.api/-service/fail-on-warnings.html?query=abstract%20val%20failOnWarnings:%20Property%3CBoolean%3E|on a service>, so it's specific to the Apollo codegen