A modern programming language that makes developers happier.

kotlinlang

Would it be possible to add a flag to allow us to treat `UnusedVariable` as an error issue instead of just warning? I can file a github issue about this if folks feel it would be useful/make sense.

Would `failOnWarnings` do the job?
<https://apollographql.github.io/apollo-kotlin/kdoc/older/4.2.0/apollo-gradle-plugin-external/com.apollographql.apollo.gradle.api/-service/fail-on-warnings.html|https://apollographql.github.io/apollo-kotlin/kdoc/older/4.2.0/apollo-gradle-plugin-exte[…]ographql.apollo.gradle.api/-service/fail-on-warnings.html>

I think the issue is that we have some deprecation warnings that we don’t want to fail on

What we really need is a way to set the level per-issue type

Yeah. A list of warnings to fail on, perhaps?

I think we might as well go all in on configurability

Ok, I lied. It looks like the deprecation warnings are gone for us…


For our current use-case it does look like `failOnWarnings` would do the job.

At some point, we'll probably need something like this though:
```{ 
  issue: UnusedVariable,
  level: Error,
},
{ 
  issue: UnusedFragment,
  level: Warning,
},
{ 
  issue: DeprecatedUsage,
  level: Ignore,
},```


Feel free to open an issue, at least for tracking

&gt; And then we need baselines 
Do you? I mean it would be nice, but it wouldn't necessarily block the per-issue configuration I think. At least I know of one high-profile project which added such configuration but doesn't have baselines support <https://kotlinlang.org/docs/whatsnew-eap.html#how-to-apply> :smirk:

Issue here for reference <https://github.com/apollographql/apollo-kotlin/issues/6516>