| 1 Apr 2024 |
|  carlosedp | 20:06:09 |
| carlosedp | I have a Quarkus / Scala 3 project that uses Maven and I'm trying to use the maven plugin to have scalafix... but it didn't work with Scala 3 syntax... | 20:06:47 |
| carlosedp | any tips? | 20:06:50 |
| carlosedp | I've opened an issue about this but nothing yet: https://github.com/evis/scalafix-maven-plugin/issues/143 | 21:19:11 |
| 5 Apr 2024 |
|  Ondřej Španěl joined the room. | 05:54:41 |
|  oclok_ joined the room. | 09:46:24 |
| 7 Apr 2024 |
|  shaked9252 changed their display name from shaked to shaked9252. | 08:27:51 |
| 8 Apr 2024 |
|  _jasperm changed their profile picture. | 07:33:24 |
| 10 Apr 2024 |
|  thanh.le joined the room. | 01:15:50 |
 channingwalton | Hi, I've noticed that using scalafix results in my project being compiled twice when doing something like this: sbt "clean;scalafix --check;test"
I am probably the last to notice … but is it possible to stop recompilation? | 16:33:12 |
 bjaglin | Since https://github.com/scalacenter/sbt-scalafix/pull/196, the compilation triggered by invoking scalafix with sbt-scalafix is not cached because it relaxes some scalacOptions (like fatal warnings) to maximize the chances of getting compilation to go through. This could probably tweaked so that compilation is cached in case none of these flags are used (I am surprised no one asked in 3 years!). But in your specific case, the easiest is to run test first. | 17:13:31 |
| bjaglin | * Since https://github.com/scalacenter/sbt-scalafix/pull/196, the compilation triggered when invoking scalafix via sbt-scalafix is not cached because it relaxes some scalacOptions (like fatal warnings) to maximize the chances of getting compilation to go through. This could probably tweaked so that compilation is cached in case none of these flags are used (I am surprised no one asked in 3 years!). But in your specific case, the easiest is to run test first. | 17:13:52 |
| bjaglin | * Since https://github.com/scalacenter/sbt-scalafix/pull/196, the compilation triggered when invoking scalafix via sbt-scalafix is not cached because it relaxes some scalacOptions (like fatal warnings) to maximize the chances of getting compilation to go through. This could probably tweaked so that compilation is cached in case none of these flags is used (I am surprised no one asked in 3 years!). But in your specific case, the easiest is to run test first. | 17:14:12 |
| channingwalton | Ah ok that make sense. I can avoid the above just by turning on scalafixOnCompile and avoiding the scalafix --check step I think. I only noticed this at work because some monstrosity is taking 100s to compile. | 17:14:49 |
| bjaglin | * Since https://github.com/scalacenter/sbt-scalafix/pull/196, the compilation triggered when invoking scalafix via sbt-scalafix is not cached because it relaxes some scalacOptions (like fatal warnings) to maximize the chances of getting compilation to go through. This could probably be tweaked so that compilation is cached in case none of these flags is used (I am surprised no one asked in 3 years!). But in your specific case, the easiest is to run test first. | 17:20:08 |
| bjaglin | * Since https://github.com/scalacenter/sbt-scalafix/pull/196, the compilation triggered when invoking scalafix via sbt-scalafix is not cached because it relaxes some scalacOptions (like fatal warnings) to maximize the chances of getting compilation to go through. This could probably be tweaked so that compilation is cached in case none of these flags is used (I am surprised no one asked in 3 years!). But in your specific case, the easiest is to run test first. | 17:21:11 |
| bjaglin | * Since https://github.com/scalacenter/sbt-scalafix/pull/196, the compilation triggered when invoking scalafix via sbt-scalafix is not cached because it relaxes some scalacOptions (like fatal warnings flags), in order to maximize the chances of getting compilation to go through. This could probably be tweaked so that compilation is cached in case none of these flags is used (I am surprised no one asked in 3 years!). But in your specific case, the easiest is to run test first. | 17:21:50 |
| bjaglin | (but you'll have to make sure the original test runs before, otherwise you'll hit the same double-compilation issue 😃 ) | 17:24:48 |
| channingwalton | Thanks, doing it last fixed the issue. I'll go with that for now as a minimal change. | 17:26:22 |
|  bumblebread. joined the room. | 22:59:06 |
| 11 Apr 2024 |
|  arturaz changed their profile picture. | 09:31:24 |
|  davesmith00000 changed their profile picture. | 10:23:05 |
| 12 Apr 2024 |
|  fel_mazo joined the room. | 09:25:33 |
|  nphardass joined the room. | 11:25:18 |
| 14 Apr 2024 |
|  sumew joined the room. | 15:49:18 |
| 15 Apr 2024 |
|  valencik changed their profile picture. | 12:31:42 |
| 16 Apr 2024 |
|  wu_lynx joined the room. | 15:44:28 |
|  jackkoenig changed their profile picture. | 20:29:15 |
|  andy.czerwonka joined the room. | 23:17:41 |
| 17 Apr 2024 |
|  ashwin1899 joined the room. | 07:25:43 |
