Brice Jaglin

/cc @poslegm - I can take the lead on that in the coming days

Ideally we should first cut a release with the hooks to be able to write scripted tests with sbt-scalafix in sbt-scalafmt.

In https://github.com/scalacenter/sbt-scalafix/pull/147#issuecomment-657057535, @olafurpg wrote: > I think it's also worth exploring another approach where we have a scalafmt rule that formats the code and we extend `.scalafmt.conf` to support running...

> We could maybe before compting the new fixed output, relying on this assertion, trigger a new compilation? Maybe I am misunderstanding, but this is indeed what I was suggesting...

@adpi2 I think I have. I will try to write a scripted.

> @adpi2 I think I have. I will try to write a scripted. Apologies, the `StaleSemanticdbError` was specific to my very adhoc setup, caused by concurrent runs of `scalafix`.

Looking at the code and seeing that patches are applied after execution of all rules, I am wondering if we should update this issue and keep it open. It seems...

Thanks for the report. I agree it's currently a pain for corporate users that resolvers and credentials are not inherited from sbt. > The plugin does not seem to respect...

Thanks for reporting! I guess there is something fishy in https://github.com/scalacenter/scalafix/blob/449a06a03d2595a1ec6f44201353881b3edc4aee/scalafix-rules/src/main/scala-2/scalafix/internal/rule/CompilerTypePrinter.scala#L299-L389 > I wonder why there is a difference there. This might be something funky going on with Metals. Probably...

Thanks, that sounds like a rule that could benefit many FP codebases indeed! It would be interesting to see the amount of false positives on a project and if/how we...