| 22 Apr 2024 |
|  renghen joined the room. | 10:02:42 |
| 23 Apr 2024 |
 bjaglin | channingwalton FTR, I have just merged https://github.com/scalacenter/sbt-scalafix/pull/411 which should improve compilation cache hit on sbt "clean;scalafix --check;test" | 20:10:13 |
| 24 Apr 2024 |
|  digitalmechanic joined the room. | 10:26:55 |
 channingwalton | awesome, thank you. | 13:04:20 |
| 25 Apr 2024 |
|  oyvindberg joined the room. | 20:48:50 |
|  Michael D changed their profile picture. | 20:57:05 |
| 26 Apr 2024 |
|  bjornregnell joined the room. | 11:40:45 |
| 27 Apr 2024 |
|  cobra8151 joined the room. | 09:53:05 |
| 30 Apr 2024 |
|  .gersondev changed their display name from gersondev to .gersondev. | 09:45:02 |
|  toniogela changed their profile picture. | 10:09:24 |
| 1 May 2024 |
| bjaglin | 🏁 sbt-scalafix & scalafix 0.12.1 are available on Maven central! Thanks to the 5 contributors to that release 🙇
Highlights
- Scalafix now runs with Scala 2.13.14 (and supports projects built with it, just like 0.12.0 thanks to scalac-semanticdb backpublishing)
- User-defined sbt resolvers are now honored for fetching scalafix & custom rules artifacts, in addition to scalafixResolvers
- scalafixScalaBinaryVersion is deprecated, as Scalafix now runs with the project scalaBinaryVersion by default (falling back to Scala 2.13 for Scala 3 sources)
- Performance improvements in sbt-scalafix: memory regression introduced in 0.12.0 fixed, incremental runs more efficient (both in memory usage & latency), and increased contribution to compilation cache (Zinc) | 20:44:43 |
| bjaglin | * 🏁 sbt-scalafix & scalafix 0.12.1 are available on Maven central! Thanks to the 5 contributors to that release 🙇
Highlights
- Scalafix now runs with Scala 2.13.14 (and supports projects built with it, just like 0.12.0 thanks to scalac-semanticdb backpublishing)
- User-defined sbt resolvers are now honored for fetching scalafix & custom rules artifacts, in addition to scalafixResolvers
- scalafixScalaBinaryVersion is deprecated, as Scalafix now runs with the project scalaBinaryVersion by default (falling back to Scala 2.13 for Scala 3 sources)
- Performance improvements in sbt-scalafix: memory regression introduced in 0.12.0 fixed, incremental runs more efficient (both in memory usage & latency), and increased contribution to compilation cache (Zinc) | 20:47:10 |
| bjaglin | * 🏁 sbt-scalafix & scalafix 0.12.1 are available on Maven central! Thanks to the 5 contributors to that release 🙇
Highlights
- Scalafix now runs with Scala 2.13.14 (and supports projects built with it, just like 0.12.0 thanks to scalac-semanticdb backpublishing)
- User-defined sbt resolvers are now honored for fetching scalafix & custom rules artifacts, in addition to scalafixResolvers
- scalafixScalaBinaryVersion is deprecated, as Scalafix now runs with the project scalaBinaryVersion by default (falling back to Scala 2.13 for Scala 3 sources)
- Performance improvements in sbt-scalafix: memory regression introduced in 0.12.0 fixed, incremental runs more efficient (both in memory usage & latency), and increased contribution to compilation cache (Zinc) | 20:48:41 |
| 2 May 2024 |
|  vt19110882 joined the room. | 19:18:52 |
| 4 May 2024 |
|  severian_au changed their display name from severian to severian_au. | 02:39:04 |
| 5 May 2024 |
| Michael D | My team is hoping to switch from SBT over to Bazel, is there a way to run scalafix using Bazel or any plans in the near future for it? | 02:22:23 |
| bjaglin | https://eed3si9n.com/automate-refactoring-with-bazel-and-scalafix/ starts to get old, but at that time it described the state of the art - from what I hear it's still rough on the edges | 07:08:27 |
| bjaglin | to answer more precisely your question: to my knowledge, at the moment, no one from the community is actively working on a plugin (I'd be happy to help out but I can't lead that since I am not a Bazel user myself), and the Scala Center does not have resources to sponsor | 07:41:37 |
| bjaglin | * to answer more precisely your question: to my knowledge, at the moment, no one from the community is actively working on a plugin (I'd be happy to help out but I can't lead that since I am not a Bazel user myself), and the Scala Center does not have resources to sponsor this initiative | 07:41:44 |
 Tomasz Godzik | We could do a workaround via metals, but not sure if that would be the best option. We could potentially add a command to run scalafix on all known files. We don't support linting thpugh | 08:47:42 |
| Tomasz Godzik | My three cents here | 08:47:50 |
| Michael D | I wouldn't mind contributing, my team is for sure going to need both scalafix and scalafmt so I at very least have the motivation to work on it. I've just never contributed to any of the projects so I wouldn't know where to start | 15:45:45 |
| bjaglin | Cool! https://github.com/scalacenter/scalafix does not provide any build tool integration (while https://github.com/scalacenter/sbt-scalafix, https://github.com/joan38/mill-scalafix, https://github.com/cosmicsilence/gradle-scalafix & https://github.com/evis/scalafix-maven-plugin do), so you'd start in your own repo anyway. | 16:57:14 |
| 6 May 2024 |
|  mrsauceman joined the room. | 16:37:16 |
| 7 May 2024 |
|  VMetals changed their display name from water_underscore to VMetals. | 07:02:00 |
|  mvillafuerte joined the room. | 13:46:31 |
| 10 May 2024 |
 .sandwichwizard | hey everyone, how can I run scalafix from the command line and get back a non-zero exit code when there are any warnings or applied patches? I thought --check would do it, but it still returns 0 when there's a warning | 15:18:06 |
| .sandwichwizard changed their display name from .sandwichwizard#0 to .sandwichwizard. | 15:18:36 |
| 12 May 2024 |
| bjaglin | Indeed, --check only returns 0 when there is no ERROR diagnostic nor pending rewrite. There is no way to have a "fatal warnings" behavior with the CLI at the moment. I suggest you open a GitHub issue to discuss semantics. Happy to provide pointers to implement it once we've agreed on that. | 17:01:14 |
| bjaglin | * Hey! Indeed, --check only returns 0 when there is no ERROR diagnostic nor pending rewrite. There is no way to have a "fatal warnings" behavior with the CLI at the moment. I suggest you open a GitHub issue to discuss semantics. Happy to provide pointers to implement it once we've agreed on that. | 17:01:17 |
