enable scalafixCaching by default #213
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjaglin
changed the title
mlachkar
approved these changes
May 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The lack of bug reports over the last year or so, despite usage of it through
scalafixOnCompile(see scalacenter/scalafix#1164 (comment) & https://github.com/search?p=3&q=scalafixOnCompile&type=Code) makes me believe the feature is mature enough for prime time. In real life, we never experienced the false positive mentioned in scalacenter/scalafix#1164 (comment), and since CI should run on a clean slate anyway, I think it's safe to say that it's only a theoretical concern.Ideally, it should move to upstream scalafix, but handling state & file stamping without sbt helpers is far from trivial.