You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sbt-scalafix automatically downloads semanticdb-scalac specified by semanticdbVersion property. sbt-scalafix defines the default semanticdb-scalac version in scalafixSemanticdb.revision property.
However, sometimes the scalameta version in scalafixSemanticdb.revision is incompatible with newer Scala.
So, users may need to set semanticdbVersion explicitly , like below:
Sounds good to me. Should we wait until scalacenter/scalafix#1146 is resolved? If I understand that correctly it will be possible in the future to set the Scalafix version (and therefore the semanticdb version) in .scalafix.conf similar to how the Scalafmt version is set in .scalafmt.conf. The implementation for this feature could then be similar to the existing implementation for Scalafmt.
This idea came up on my mind on scalacenter/scalafix#1183
sbt-scalafix
automatically downloadssemanticdb-scalac
specified bysemanticdbVersion
property.sbt-scalafix
defines the defaultsemanticdb-scalac
version inscalafixSemanticdb.revision
property.However, sometimes the scalameta version in
scalafixSemanticdb.revision
is incompatible with newer Scala.So, users may need to set
semanticdbVersion
explicitly , like below:However, this is not good since the version need manual update when newer version of scalameta/sbt-scalafix are published.
I think Scala Steward can save such manual updating
semanticdbVersion
, like doing so on scalafmt or sbt.The text was updated successfully, but these errors were encountered: