Ólafur Páll Geirsson

The org.scalafmt.config package is not public API, neo-sbt-scalafmt should follow the recommendations I made here https://github.com/lucidsoftware/neo-sbt-scalafmt/pull/36#issuecomment-321938150 to use the following methods https://github.com/scalameta/scalafmt/blob/4a5b7681933fa1a1c289d5fa5aa8a4abfe8a71c9/scalafmt-core/shared/src/main/scala/org/scalafmt/Scalafmt.scala#L77-L89

Took a while for me to get back to this! This should be fixed in the next release (I think targeted for July 10th)

For what it's worth, the vim installation instructions use vim-lsc directly without a custom Metals package https://scalameta.org/metals/docs/editors/vim.html. My impression is that this is working OK for people, at least no...

Unhandled case ```scala check("if (a) (if (b) c) else d") java.lang.RuntimeException: AST changed obtained: if (a) if (b) c else d expected: if (a) (if (b) c) else d ```...

Discovered by @japgolly in https://github.com/scalameta/scalafmt/pull/1122

Is this PR still relevant?

Thank you for reporting! Moving this issue to feature requests

Related discussion in https://gitter.im/scalameta/metals?at=5cc167b54b4cb471d953beaa on the expected behavior of "preferred platform"

First step towards implementing this feature https://github.com/scalameta/metals/pull/948. The next step would be to expose configuration to to customize the priority when selecting a single build target from multiple candidates.

BSP is already able to represent cross-built projects. The reason you get "no build target" for Dotty sources is that `sbt bloopInstall` only exports the build for one `scalaVersion`. In...