-
Notifications
You must be signed in to change notification settings - Fork 502
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
use scalafixAll #1523
use scalafixAll #1523
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1523 +/- ##
==========================================
- Coverage 70.11% 70.07% -0.04%
==========================================
Files 112 112
Lines 1780 1778 -2
Branches 50 48 -2
==========================================
- Hits 1248 1246 -2
Misses 532 532
Continue to review full report at Codecov.
|
This slightly improves runtime as migrations can be run in parallel for Compile and Test. Note that this will NOT run migrations on IntegrationTest or any other custom configuration, as Scalafix needs to be enabled explicitly on them. https://github.com/scalacenter/scalafix/blob/v0.9.18/docs/users/installation.md#integration-tests
Maybe slightly off topic, but I wonder if there is a demand for that in the context of scala-steward? If so, it could be interesting to provide a |
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.
LGTM. Many thanks @bjaglin!
Nobody has asked for this yet or complained about it but I guess it makes sense to have something like |
For the record, following up in scalacenter/scalafix#1197 |
Use scalacenter/sbt-scalafix#126, released in sbt-scalafix 0.9.18.
This slightly improves runtime as migrations can be run in parallel for
Compile
andTest
.Note that this will NOT run migrations on
IntegrationTest
or any other custom configuration, as Scalafix needs to be enabled explicitly on them.