Enable :warnings_as_errors for CI only
Alright I'm gonna be bold here and suggest we disable the :warnings_as_errors
feature except in CI. Here's why:
-
When it fails, it has to start recompilation over. Not a big deal for 1 file, but painful for 538 files. This massively slows down local development, and sometimes you have to do it multiple times before fixing everything.
-
By keeping it on during CI, we'll ensure no warnings make it into the develop branch.
-
You can still see warnings in your console.
-
We already have checks that run during CI only - lint, credo, cycles... checking for warnings isn't any different or special, and does not need to be enforced at compile-time.
-
Devs can configure their local dev environment to do just about anything, including checking for warnings.
I know I'm not the only one being slowed down by this.