Skip to content
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

Add in scalafmt and scalafix. #333

Merged
merged 1 commit into from
May 13, 2021
Merged

Add in scalafmt and scalafix. #333

merged 1 commit into from
May 13, 2021

Conversation

ckipp01
Copy link
Member

@ckipp01 ckipp01 commented May 11, 2021

I was going to wait to do this, but I was starting on something else in
here and I kept hitting format by habit since I'm honestly just used to
always having it. I think it's safe to say that most Scala developers
will be used to the default style that scalafmt gives you, so I'd like
to propose that we add this in along with scalafix to organize imports.

One huge concern is always that changes like this make it hard to get a
good git blame, however with modern git, this really isn't an issue
anymore. You can read more about his here:
https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame

I recently used the strategy outlined in that article in the
sbt-scoverage plugin:
scoverage/sbt-scoverage#351 and it seems to work
quite well.

I'll leave this open for now just to see if there is any opposition from any interested
parties. If not, I'll merge this is and follow it up with a pr introducing a .git-blame-ignore-revs
which can then be used to locally ignore the entire commit when using git blame. Then
we won't lose any usefulness of the blame.

I was going to wait to do this, but I was starting on something else in
here and I kept hitting format by habit since I'm honestly just used to
always having it. I think it's safe to say that most Scala developers
will be used to the default style that scalafmt gives you, so I'd like
to propose that we add this in along with scalafix to organize imports.

One huge concern is always that changes like this make it hard to get a
good `git blame`, however with modern git, this really isn't an issue
anymore. You can read more about his here:
https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame

I recently used the strategy outlined in that article in the
sbt-scoverage plugin:
scoverage/sbt-scoverage#351 and it seems to work
quite well.
@ckipp01 ckipp01 marked this pull request as ready for review May 13, 2021 13:05
@ckipp01 ckipp01 merged commit 03aeb37 into scoverage:main May 13, 2021
@ckipp01 ckipp01 deleted the formatting branch May 13, 2021 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant