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

Upgrade Scalafmt to 3.8.3 #4566

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

jackkoenig
Copy link
Contributor

@jackkoenig jackkoenig commented Dec 17, 2024

As you can see, there's a bit of a diff. I've done the best I can to minimize it but there's some diff.

It seems to try to keep argument lists on one line, which I like, but it does it even if an early argument list was split between multiple lines which is a bit weird.

It also likes keeping case on the same line as the { which I like, although occasionally that leads to longish lines. Anyway, we can try to massage this further or just go with it. I think it's fine but am curious what others think.

We will need to bump Scalafmt soon in order to support Scala 3.

Contributor Checklist

  • Did you add Scaladoc to every public function/method?
  • Did you add at least one test demonstrating the PR?
  • Did you delete any extraneous printlns/debugging code?
  • Did you specify the type of improvement?
  • Did you add appropriate documentation in docs/src?
  • Did you request a desired merge strategy?
  • Did you add text to be included in the Release Notes for this change?

Type of Improvement

  • Internal or build-related (includes code refactoring/cleanup)

Desired Merge Strategy

  • Squash

Release Notes

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.6.x, 5.x, or 6.x depending on impact, API modification or big change: 7.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

@jackkoenig jackkoenig added the Internal Internal change, does not affect users, will be included in release notes label Dec 17, 2024
@jackkoenig jackkoenig added this to the 7.0 milestone Dec 17, 2024
n: Int
)(gen: (Int) => T
)(
n: Int
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is prettier

Copy link
Contributor

@mwachs5 mwachs5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the spot checks of what i saw look nice. The alignment on => is definitely more aggressive, that would be the only thing I'd wonder if you want to turn off but I also like it if we're erring on the side of alignment

Copy link
Contributor

@azidar azidar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I definitely like putting the case on the same line! Overall I think its good.

def known: Boolean = false
def get: Int = None.get
def known: Boolean = false
def get: Int = None.get
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit strange to me to align the types, but not the = ? But I suppose that might be a much larger diff, which is fine to avoid.

@jackkoenig jackkoenig force-pushed the jackkoenig/upgrade-scalafmt branch from 37c9adc to 5f7e78b Compare December 18, 2024 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal Internal change, does not affect users, will be included in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants