Optionally disable `-Xfatal-warnings`? about sbt-tpolecat HOT 3 CLOSED

@timbertson-zd I would definitely welcome a PR for that! 👍 You may also be interested in the discussion on #10 as we talked a little bit about adding a "development mode" and "release mode" concept to the plugin?

from sbt-tpolecat.

Thanks. I had a crack at it, but honestly anything I thought up felt kind of awkward. I've decided to just be a little more opinionated in sbt-strict-scope, to automatically filter out any options that are enabled in strict mode:

https://github.com/timbertson/sbt-strict-scope/blob/94cae04944e62372a58af802b08cd160f5c2b418/src/main/scala/net/gfxmonk/sbt/StrictScope.scala#L28-L29

Honestly I don't understand enough SBT to know if this is reliable, though it did seem to work in my testing. I've asked on SO in case anyone knows: https://stackoverflow.com/questions/63532441/how-to-determine-control-the-order-of-operations-when-modifying-sbt-taskkey-se

I think if I did make a sbt-strict-scope-tpolecat which was the same plugin but also depended on this one, that would probably force the ordering I want. As long as "settings application order" follows "plugin initializaion order" 🤞 . But who knows 🤷

from sbt-tpolecat.

I often use an Autoplugin

import sbt.*
import sbt.Keys.*

object NoFatalWarningsPlugin extends AutoPlugin {
  override def trigger = allRequirements

  override lazy val projectSettings: Seq[Setting[?]] = Seq(
    scalacOptions --= {
      if (!sys.env.contains("CI"))
        Seq("-Xfatal-warnings", "-Ywarn-unused", "-Ywarn-unused-import")
      else
        Seq.empty
    }
  )
}

or simply common setting for modules

val scalacLocally: Seq[Def.Setting[_]] = {
  if (!sys.env.contains("CI")) {
    Seq(scalacOptions -= "-Xfatal-warnings")
  } else {
    Seq()
  }
}

from sbt-tpolecat.