Brice Jaglin

Thanks for the report! > However, in this case, rules was not missing, merely empty :) Indeed, I guess a better wording could be "no rule requested to run" (since...

For the context: for sbt-scalafix users, running `scalafix` without any configuration-provided nor CLI-provided rule means that the invocation is a no-op, which is most likely a setup issue, thus the...

Technically speaking, we could try wrapping https://github.com/scalacenter/scalafix/blob/57042bd97ef97e832c2701eecc6770672b980492/scalafix-cli/src/main/scala/scalafix/internal/v1/Args.scala#L54 in an `Option` to see whether we can have a no-op, non-failing behavior with an explicit empty list of rules. I do feel...

> I'm not sure if it's the wrong level. It depends on whether you consider this an issue specific to sbt-scalafix or scalafix in general, in which case the .scalafix.conf...

Thanks for the report! For the record, https://github.com/scalacenter/scalafix/pull/1163 recently reduced false negatives when checking against `scalacOptions` in `RemoveUnused`. Regarding the usage of `-Wconf`: from my understanding it's only a way...

Thanks to @mlachkar, there has been good progress in [inferring the parsing dialect based on the provided `scalaVersion` CLI/API args](https://github.com/scalacenter/scalafix/pull/1392), and the sbt-scalafix companion with support for the built-in dotty...

Regarding (2) and (3): actually most of the patches take strings as parameters to inject (except `addGlobalImport` which seems to be the only factory method for `Patch` that can take...

@tgodzik thanks for the prompt feedback and your hard work on Scala 3 support in scalameta! I/we will follow-up on scalameta as the needs materialize. As mentioned above, I probably...

> Some other things that might be useful would be to be able to declare different rules for a subset of files. We could have similar thing to `fileOverrides` in...

@rvacaru I am going to update the description now and will tick the box once we have the artifacts published