scalafix
scalafix copied to clipboard
scalacenter
Refactoring and linting tool for Scala
For example, with `--scalac-options`, the only documentation I could find looked like `--scalac-options -Ywarn-unused`. If I had 2 options, `A` and `B`, I wouldn't know how to pass them as...
I wrote a linter for all of the internal services at my company, as an sbt plugin. Part of the linting process involves running scalafix. It would be nice if...
**Problem** When writing linting rules which can possibly do a autofix/rewrite, it would be nice to have an option to run all linting rules to see what the errors were...
before : ``` private var upstreamFailed: OptionVal[Throwable] = OptionVal.None ``` after ``` OptionVal.None ``` source :akka.stream.impl.fusing.ActorGraphInterpreter.ActorOutputBoundary
Reported by @xeno-by , the current scheme of inserting a named import and leaving wildcard imports unchanged can produce ambiguous imports, even if named imports have higher precedence ```scala scala>...
Sorry, yet-another-upstream-idea 😁 The idea is basically to turn this example project into a plugin: https://github.com/olafurpg/scalafix-codegen/blob/7fdaa50a94cc31ae7af2d2237c91bc9611b17fe1/build.sbt I know it's a small snippet, but after copying it between a few projects...
Follows https://github.com/scalacenter/scalafix/pull/1664#pullrequestreview-1096671581
From https://github.com/scalacenter/scalafix/pull/1650#discussion_r948473083 > See https://github.com/scalacenter/scalafix/issues/1172#issuecomment-646621781 for the context of why we build/publish against an old version. For the next breaking change version of scalafix, I believe we should remove support...
For ExplicitResultTypes to work out of the box, it would better to set by default ``` scalafixScalaBinaryVersion := scalaBinaryVersion.value ``` Current blockers: - confirm all major rules are cross-published in...