Separated defns get aligned since 3.0.5

[yurique]

• Version: 3.0.5
• Configuration:

version=3.0.5
runner.dialect = "scala213"
fileOverride {
  "glob:**/scala-3/**" {
    runner.dialect = scala3
  }
}
style = defaultWithAlign
align.openParenCallSite = true
align.openParenDefnSite = true
align.arrowEnumeratorGenerator = true
maxColumn = 160
continuationIndent.defnSite = 2
assumeStandardLibraryStripMargin = true
danglingParentheses.defnSite = true
danglingParentheses.callSite = true
rewrite.rules = [AvoidInfix, ExpandImportSelectors, RedundantParens, SortModifiers]
docstrings = JavaDoc
newlines.afterCurlyLambda = preserve
docstrings.style = Asterisk
docstrings.oneline = unfold
trailingCommas = "preserve"
optIn.breaksInsideChains = true
includeCurlyBraceInSelectChains = true
//includeNoParensInSelectChains = true
binPack.parentConstructors="never"
//newlines.source="keep"
align.preset = most

Steps

Update scalafmt version from 3.0.4 to 3.0.5.

Example:
https://github.com/tulz-app/laminext/pull/72/files

Given code like this:

  override protected[this] def onStart(): Unit = {
    startCallback()
    super.onStart()
  }

  override protected[this] def onStop(): Unit = {
    stopCallback()
    super.onStop()
  }

When I run scalafmt like this:

via the sbt-scalafmt plugin.

Problem

Scalafmt formats code like this (there are more defs in the file, so the = got aligned with the furthest one):

  override protected[this] def onStart(): Unit                                         = {
    startCallback()
    super.onStart()
  }

  override protected[this] def onStop(): Unit                                          = {
    stopCallback()
    super.onStop()
  }

Expectation

I would like the formatted output to look like this (same as original, as it was already correctly formatted with 3.0.4):

  override protected[this] def onStart(): Unit = {
    startCallback()
    super.onStart()
  }

  override protected[this] def onStop(): Unit = {
    stopCallback()
    super.onStop()
  }

Notes

This might be related to this PR: #2753

[github-dimitri-ho]

It seems to happen only when one of the methods in the object / class has a scope modifier

[yurique]

in the same example PR, same formatting got applied to the lazy vals in the build.sbt: https://github.com/tulz-app/laminext/pull/72/files#diff-5634c415cd8c8504fdb973a3ed092300b43c4b8fc1e184f7249eb29a55511f91

[poslegm]

Another example: poslegm/munit-zio@50387ef