Máté Karácsony
Máté Karácsony
The source I could find is pretty old at this point: https://github.com/ianoc/bazel-scalafix If I understand it right, it uses a [wrapper script](https://github.com/ianoc/bazel-scalafix/blob/master/scripts/run-scalafix) to run scalafix, that is: 1. Collecting targets...
After taking a quick look at the cli args of scalafix, it seems to me that collecting the classpath is still being required besides having SemanticDB.
I'm thinking if putting a Bazel aspect on `_scalac` or some other attribute would be a good idea here, then using that aspect to build a minimal scalafix wrapper script....
Yeah thanks, I was also thinking about having a custom shim to forward args in a file (there will be a "few" if I add all jars, etc). But, if...
I have a version working in our own repo, but I'd like to contribute this back to `rules_scala` if there's interest. However, there are a few things to be cleared...
Also I noted when I turn on semanticdb on the toolchain I get tons of output on each bazel build like: ``` DT:bazel-out/darwin_arm64-fastbuild/bin/external/io_bazel_rules_scala_scala_library/io_bazel_rules_scala_scala_library.stamp/scala-library-2.12.18-stamped.jar ```
Are there any progress / plans around this?
Oh, ok, thanks!
Can we have a release for 2.12.18 as well please? 🥺
I even have a PR now: https://github.com/tek/splain/pull/124. I'm forced to use a self-built artifact for now I guess.