Scalafmt #147
Closed
Scalafmt #147
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
tdroxler
force-pushed
the
scalafmt
branch
7 times, most recently
from
76a9c45 to
ff6539f
Compare
tdroxler
force-pushed
the
scalafmt
branch
2 times, most recently
from
4fe3c73 to
eb2d9fb
Compare
|
I added the scalafmt check in CI, also took the opportunity to use |
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.
I think I found a good tradeoff that introduces very little changes. I see two main ones:
types of functions are move to the next line
Class definition, when there is enough place into the 120 columns, they are put in one line
Beside that, no big changes