-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scalafix: leverage scalafixEnable & scalafixAll #550
Conversation
1198757
to
3f754f6
Compare
README.md
Outdated
|
||
```scala | ||
// project/plugins.sbt | ||
addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "0.9.34") | ||
addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "0.10.1") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's hold the merge of that doc, as invalid code may be generated when scalafix 0.10.x runs a version of the migration prior to #549
libraryDependencies += "org.scala-lang.modules" %% "scala-collection-compat" % "<version>" | ||
addCompilerPlugin(scalafixSemanticdb) | ||
scalacOptions ++= List("-Yrangepos", "-P:semanticdb:synthetics:on") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, synthetics are used in the rule, so we'll need to keep that :(
you're saying we should roll a release, then merge this? do I understand correctly? |
okay; release ticket #552 |
thanks @bjaglin ! |
The
scalafixEnable
command is used by scala-steward for more than 3 years and got some further improvements lately, so I think it's safe to rely on it instead of asking users to update their build.